-
Notifications
You must be signed in to change notification settings - Fork 272
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
Revisit Geany-Plugins strings marked as translatable #248
Comments
Odd indeed
A bit odd too, but I could imagine someone wanting to translate some of them, e.g. for languages having other alphabets including numbers (I don't know but e.g. Chinese, Japanese or Hebrew might fall in this category).
This however looks plain wrong
While they might be suboptimal, and surely should have a specific comment explaining what they mean to the translators, they do make sense. E.g. in French typography you want to put a non-breakable space before colons (
Those are very weird indeed. |
These are not the only weird translations. During my work on German translation I found a huge number of at least unclear strings containing. To be fair, I didn't report or fix most of them just grumbling into my beard. However, I would leave this open as an 1.26 issue "Revisitng strings of g-p project" |
Agreed. I have some other griefs against the current strings, like plugins having the word "plugin" in their description, and missing ellipsis on some menu items. I worked some of them around in the French translation, but we should properly fix the original strings after 1.25. |
@b4n Please create new issues/PR with reference to this issue |
New author in translation strings:
|
geanypg - translatable author
Is it really needed for author to be translatable?
Just numbers
Tough in some languages, e.g. I found that:
Empty formatters
And others:
Symbols
P.S. Searched using multiline regexp
msgid (.+)\nmsgstr \1
The text was updated successfully, but these errors were encountered: