GNOME Bugzilla – Bug 672457
untranslatable string (or confusing UI)
Last modified: 2016-03-31 13:57:32 UTC
Created attachment 210163 [details] screenshot with 'no password' In the box creation summary, there's a "Password: no password" entry, which is not marked as translateable. Seeing this and some recent discussions, I'm not 100% whether this means the box doesn't have a password (shouldn't this be hidden in this case?), or if it means that the box uses a default password which is "no password", in which case we probably should use something less confusing (ie some non-security related word like gnome or boxes or anything :)
(In reply to comment #0) > Created an attachment (id=210163) [details] > screenshot with 'no password' > > In the box creation summary, there's a "Password: no password" entry, which is > not marked as translateable. It should be but there is a string freeze in effect right now. Could be fixed in a separate branch though.. > Seeing this and some recent discussions, I'm not > 100% whether this means the box doesn't have a password (shouldn't this be > hidden in this case?), or if it means that the box uses a default password > which is "no password", in which case we probably should use something less > confusing (ie some non-security related word like gnome or boxes or anything :) You are getting confused with bug#670306, which is only about a fedora-specific issue. To me 'no password' with spaces clearly means what it says: no password. Perhaps it could be made even more clear so suggestion with 1-liner patch welcome!
(In reply to comment #1) > (In reply to comment #0) > > Created an attachment (id=210163) [details] [details] > > screenshot with 'no password' > > > > In the box creation summary, there's a "Password: no password" entry, which is > > not marked as translateable. > > It should be but there is a string freeze in effect right now. Could be fixed > in a separate branch though.. > Marking a string which is already present as translatable is not considered breaking string freeze, though it's always possible to formally ask for a string break if you want to be 100% sure. Adding a new string that was not there previously is breaking the string freeze.
(In reply to comment #2) > (In reply to comment #1) > > (In reply to comment #0) > > > Created an attachment (id=210163) [details] [details] [details] > > > screenshot with 'no password' > > > > > > In the box creation summary, there's a "Password: no password" entry, which is > > > not marked as translateable. > > > > It should be but there is a string freeze in effect right now. Could be fixed > > in a separate branch though.. > > > > Marking a string which is already present as translatable is not considered > breaking string freeze, You are wrong! https://live.gnome.org/TranslationProject/HandlingStringFreezes . From the POV of translators, making an existing string for translation and adding a completely new string for translation are quite the same thing.
Zeeshan: Oh please read it first. Quote: What changes are not affected by the string freeze? Change or addition of a message that is not marked for translation.
(In reply to comment #4) > Zeeshan: Oh please read it first. > Quote: > > What changes are not affected by the string freeze? > Change or addition of a message that is not marked for translation. How does that translate to "Marking a message for translation"?
(In reply to comment #3) > . From the POV of translators, making an existing string for translation and > adding a completely new string for translation are quite the same thing. Nope, this is different, in the first case, there *is* a string in the UI that cannot be translated, in the second case, you *add* an untranslated string in the UI. It is marking the string as translatable that does not change a lot for the translator (if it was already present): at worse, it will stay untranslated as before, and in the best case the translator will get a chance to tranlate it. The only difference this makes for tranlators is in statistics.
Andre quoted the wrong part of it, but he also invited you to actually read this page... "What changes are not affected by the string freeze? The following types of changes do not need explicit approval, however we would still very much like them to be announced so that we know about them: Marking a message for translation that was previously not marked for translation by accident."
Now teuf was faster, but still posting what my answer would have been: Heh, okay... Feel free to edit the wikipage so it makes sense for you. Note that there is also already: "The following types of changes do not need explicit approval, however we would still very much like them to be announced so that we know about them: Marking a message for translation that was previously not marked for translation by accident." So please fix it and inform gnome-i18n@ about it. Thanks. :)
Done!