On Sat, 4 Apr 2009 23:28:31 +0100
Klaus Ethgen <klaus+gee...@ethgen.de> wrote:

> Hi,
> 

Hi Klaus,

> I did some update to de.po, the German translation. Within I found
> something odd. Is it really necessary to translate strings like "D65",
> "D75" (well, maybe, could be written other way in Chinese, but I think
> that is a fix phrase.) or even more "%s\n\"%s\""? 

This is needed. In french we don't use such double quotes but «» instead for 
example.
About D65 and al. i guess it is almost fixed so imho this can be removed from
translatable strings.

> Additional there is
> some internationalised strings in cellrenderericon.c which I do not know
> where it is for and so I am not clear how to translate it. I think that
> text is just internal used. ("Pixbuf Object" for strong example)

Yes, since those will be never displayed we can drop them from translations.

> 
> Apart from that I found some cases where the same word has to be
> translated different in different context. So my first patch add
> pgettext for this cases. I am not completely sure if I did the
> implementation correct (well, at least it works). I just copied the
> gettext.h from my local gettext installation to the src tree and use
> that header. But I think that is dirty and there must be a other method
> to use pgettext. The documentation is quiet about the point how to have
> that function in source it only tells how that function works. I did a
> full night searching for how to implement those stuff cleanly.
> 

Such stuff may help.

> However, the second patch is the update of the translation. I am at 78%
> at the moment but will go on the next days. After all I
> just added myself to the README file. :-)

Good work ;)

> 
> For the other languages, I think it is necessary to rework them at all.
> In the German PO file I did found many wrong fuzzy translations. Many of
> them was just stupid but other did negate the sense completely. So I
> start over reviewing all fuzzy translations. (Well, I also found a bug
> in gen_translations_stats.sh if there is no fuzzy but untranslated
> strings in a po file. But that was not subject to fix for now.)

Please fix it ;)

> 
> But if the German locales are that bad how would be the other!? I think
> it is better to have no translation than such wrong ones.

I agree, any translation under 50% and older than one year shouldn't go in. 

Regards,

-- 
Laurent MONIN aka Zas

------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Geeqie-devel mailing list
Geeqie-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geeqie-devel

Reply via email to