New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Discussion] Add comment to Command, ToolTip. #167
Comments
@chennes @luzpaz PS. |
Very interesting, I never thought of that! In English it is sometimes acceptable to add the article, but I'm sure there are cases where it is not. I suggest that a more robust fix is to add a disambiguation string, so that even in cases where the English is the same for both, other languages are not tied to that. |
QT_TR_NOOP don't accept disambiguation string:( |
Those were added in Qt 5.12 I think, so maybe in 0.21 that's a reason to bump our required Qt version. |
No, I'm wrong, QT_TRANSLATE_NOOP3 has been with us for some time, it's fair game right now. |
|
@chennes I play with different type of comments
produce
I have only one idea (Use of QT_TRANSLATE_NOOP3 need big refactor). Change upper-case letter in tooltip |
The time is right for a big refactor, IMO: we're going to tag the 0.20 release tomorrow night, and then we can start making some of the big changes we've talked about. |
I'm bringing this up again now in advance of the 0.21 feature freeze: the big problem with switching to |
Bah, it gets pretty ugly. I'm back to your original solution! I'm going to ask for some help on the forums to generate a list of the command where this is a problem. Maybe we can even code this into the cMake file to force developers to do it 😄 . |
Thanks to the regex wizards on the forums, we have the following list of commands whose tooltips should be changed so they don't match their commands:
|
I suggest adding a comment for tool-tip and command names to facilitate translation. (Since it is sometimes difficult to determine this command name or its tool-tip (description) from the text)
Example.
Change
to
This text will be
in the .ts file.
This can be done after 0.20 release.
The text was updated successfully, but these errors were encountered: