GNOME Bugzilla – Bug 642135
bad UI strings (also i18n)
Last modified: 2012-02-08 16:59:07 UTC
This is not a proper sentence (actually two sentences, incorrect comma usage): #: ../js/ui/status/bluetooth.js:243 #, c-format msgid "The requested device cannot be browsed, error is '%s'" This string needs a context marker to make clear this is about audio: #: ../js/ui/status/volume.js:42 msgid "Volume"
Created attachment 195867 [details] [review] volume: Clarify translatable string Fix for the second issue - does adding context constitute a string freeze break?
Comment on attachment 195867 [details] [review] volume: Clarify translatable string > Fix for the second issue - does adding context constitute a string freeze > break? I think so. Try "make update-po" in po/ and see. IIRC, this will mark the existing translation "fuzzy", which means it won't be output into the .gmo file until someone verifies that it's correct and marks it unfuzzy. You could just fix up the .po files by hand though (where "by hand" probably means "by perl"). (It's possible that some of the existing translations are for the wrong sense of "volume", but if so, you're not making things worse, and someone will eventually report the mistranslation.)
Context markers are used to disambiguate identical strings, not to explain what something means. To just explain what a string is about, simply use comments (no string freeze break needed :-) https://live.gnome.org/TranslationProject/DevGuidelines/Use comments
Created attachment 195980 [details] [review] volume: Clarify translatable string (In reply to comment #3) > To just explain what a string is about, simply use comments Sure, can do ...
Review of attachment 195980 [details] [review]: Looks good
Attachment 195980 [details] pushed as aa2a63b - volume: Clarify translatable string