Re: wrong translations of gconf key values

On Wed, Jan 28, 2009 at 11:25 PM, Andre Klapper <ak-47 gmx net> wrote:
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 .

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
"") that these values should not be translated, but to lots
of other translators it's not.
In aloriel proposes to
add a comment to each of these strings.

Other opinions/comments?


I agree that literals or constant shouldn't be translated as they are explicit invariant values contained within the source.
I would try -- not to translate literal values enclosed within double quotes.

Are literal values only encountered for files ending with


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]