GNOME Bugzilla – Bug 569493
wrong gconf key value translations in nautilus
Last modified: 2009-03-09 20:29:27 UTC
./nso.po-#: libnautilus-private/apps_nautilus_preferences.schemas.in.h:1 ./nso.po-msgid "" ./nso.po-"A list of captions below an icon in the icon view and the desktop. The " ./nso.po:"actual number of captions shown depends on the zoom level. Possible values " ./nso.po-"are: \"size\", \"type\", \"date_modified\", \"date_changed\", \"date_accessed" ./nso.po-"\", \"owner\", \"group\", \"permissions\", \"octal_permissions\" and " ./nso.po-"\"mime_type\"." ./nso.po-msgstr "" ./nso.po-"Lelokelelo la ditlhaka kgolo ka tlase ga leswao tebelelong ya leswao le " ./nso.po-"tesekeng. Nomoro ya kgonthe ya ditlhaka-kgolo tše bontšhitšwego e ithekgile " ./nso.po-"ka mogato wa go godiša le go theoša. Boleng bjo kgonegago ke: \"bogolo\", " ./nso.po-"\"mohuta\", \"letšatši le e_mpshafaditšwego\", \"letšatši-kgwedi le " -- These values are gconf values. Being a user, you MUST set the ENGLISH value if you want to change the value of the key manually, e.g. by using gconf-editor. It is IMPOSSIBLE for users of this language to GUESS the english values if you translate the values ONLY to your language. Proposal: Put your translation in brakets after the english value. Example: " "english_value" (translation_of_english_value) " Please also check the other strings in the affected po file - I only grep'ed for one example string. You could search for "schemas.in" for example. It might be worth to bring up and explain this problem (gconf key values should remain in english) to the other translators of your team to avoid this happening in the future. As this is a general problem I have asked for discussion at http://mail.gnome.org/archives/gnome-i18n/2009-January/msg00477.html
Fixes submitted to Vertimus: http://l10n.gnome.org/vertimus/nautilus/HEAD/po/nso Mmmm, any way to commit from the interface?
Created attachment 127438 [details] Fixed naughty lus file. Just in case I can't get this commited, here is the file that fixes this issue.
you can't commit from vertimus, but you have an svn account :)
(In reply to comment #3) > you can't commit from vertimus, but you have an svn account :) > Indeed I do and it worked! That must count as terribly lazy, sorry but thought I'd not made the great Subversion migration. r15075 fixes this issue.