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
Some sentences do not need to be marked as translatable. #1002
Comments
In graphics programs there are some effects like filters that are untranslatable or aren't worth |
There's nothing inherently untranslatable about 'Gaussian blur' or 'bokeh'. The choice of translating or not translating should be left to the translators of each language. |
Some of these do seem redundant, but for the ones with two parts/sections I could see the potential necessity of letting translators reorder components by the convention of their language (right-to-left languages in particular, I guess). I am no i18n expert, but that seems like one reason to keep those. |
Based on my (admittedly limited) understanding of doing i18n for rtl scripts, it seems most of these instances do need to be marked as translatable. The only one I cannot see any reason for is {tooltip} (notice the colon in the {dname} instance), but seeing as most languages will just copy these verbatim (if we want to keep track of completion) or leave them empty, I think we can overlook that one. |
I'm not 100% sure but in my opinion, we don't need to mark as translatable these sentences.
These sentences have taken from MyPaint 2.x master branch.
The text was updated successfully, but these errors were encountered: