Re: wrong translations of gconf key values

2009-02-04 Thread Leonardo Ferreira Fontenelle
On Wed, 28 Jan 2009 18:55:37 +0100, Andre Klapper ak...@gmx.net said: 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

Re: gconf translation QA checker for keys (was Re: wrong translations of gconf key values)

2009-02-02 Thread Dwayne Bailey
On Fri, 2009-01-30 at 16:27 -0500, Og Maciel wrote: First off, w00t! :) pofilter is a great tool and this new test will definitely help us to keep our QA in shape. And if you going to FOSDEM make sure you meet the two Translate.org.za dev's whole be there. Friedel and Walter will be happy

Re: gconf translation QA checker for keys (was Re: wrong translations of gconf key values)

2009-01-31 Thread Jorge González González
El vie, 30-01-2009 a las 15:11 +0200, Dwayne Bailey escribió: OK, I promised a test to find these errors and here it is... I'm a sucker for writing QA checks. Stats = I've only tested these teams: Spanish: 35 strings Dzongkha: 8 strings French: 9 strings German: 7 Strings

Re: wrong translations of gconf key values

2009-01-29 Thread Dwayne Bailey
On Thu, 2009-01-29 at 09:10 +0200, Dwayne Bailey wrote: On Wed, 2009-01-28 at 18:55 +0100, Andre Klapper wrote: snip Example: msgid Possible values are \always\, \bonded\. bad msgstr Los valores posibles son: «siempre», «vinculados». good msgstr Los valores posibles son: «always»

wrong translations of gconf key values

2009-01-28 Thread Andre Klapper
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

Re: wrong translations of gconf key values

2009-01-28 Thread Og Maciel
+1 for adding comments to the strings. Some translators may use poedit while doing their work and won't see the source code file name associated with the string. -- Og B. Maciel omac...@foresightlinux.org ogmac...@gnome.org ogmac...@ubuntu.com GPG Keys: D5CFC202 http://www.ogmaciel.com (en_US)

Re: wrong translations of gconf key values

2009-01-28 Thread Deniz Koçak
On Wed, Jan 28, 2009 at 9:31 PM, Og Maciel ogmac...@gnome.org wrote: +1 for adding comments to the strings. +1 for comments, but what is the idea of developers about always warning translators? Some translators may use poedit while doing their work and won't see the source code file name

Re: wrong translations of gconf key values

2009-01-28 Thread Jorge González González
El mié, 28-01-2009 a las 18:55 +0100, Andre Klapper escribió: 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

Re: wrong translations of gconf key values

2009-01-28 Thread Leonardo F. Fontenelle
Em Qua, 2009-01-28 às 21:56 +0200, Deniz Koçak escreveu: On Wed, Jan 28, 2009 at 9:31 PM, Og Maciel ogmac...@gnome.org wrote: +1 for adding comments to the strings. +1 for comments, but what is the idea of developers about always warning translators? It would be great if somehow the