Iep!
Em sembla que algunes vegada no havíem acabat de decidir-nos sobre quina
era la millor opció, doncs aquí la teniu, vigileu amb els .schemas.in!!
Salut!
--
gil forcada
[ca] guifi.net - una xarxa lliure que no para de créixer
[en] guifi.net - a non-stopping free network
bloc: http://gil.badall.net
--- Begin Message ---
Dear translators,
Gconf key values should not be translated to your language only (by
dropping the original english string) because it makes it impossible for
users to set them manually, e.g. by using gconf-editor.
That is what the literal quotes should imply, see
http://live.gnome.org/TranslationProject/DevGuidelines/Enclose%20literal%20values%20in%20double%20quotes
.
Example:
msgid "Possible values are \"always\", "\"bonded\"."
bad msgstr "Los valores posibles son: «siempre», «vinculados».
good msgstr "Los valores posibles son: «always» (siempre), «bonded»
(vinculados)."
I've grep'ed the evolution po files and found 37 wrong po files.
Nautilus: 21 po files. Epiphany: 20 po files.
While I'm going to file bug reports for the rest of the evening I ask
you how to avoid this. :-)
To me it's obvious by looking at the filename of the string (ending with
".schemas.in") that these values should not be translated, but to lots
of other translators it's not.
In http://bugzilla.gnome.org/show_bug.cgi?id=569457 aloriel proposes to
add a comment to each of these strings.
Other opinions/comments?
andre
--
mailto:[email protected] | failed
http://www.iomc.de/ | http://blogs.gnome.org/aklapper
_______________________________________________
gnome-i18n mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/gnome-i18n
--- End Message ---
_______________________________________________
GNOME mailing list
[email protected]
http://llistes.softcatala.org/mailman/listinfo/gnome
