On ne 5. dubna 2009, Klaus Ethgen wrote:
> Hi,
>
> 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\""? 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)
>
It seems to be Gtk policy to translate such strings, but I agree that it does
not make much sense for Geeqie, since we are sure that the strings are not
shown in UI.
> 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.
>
Do we really need pgettext? I think that in most cases the problem is already
in the English string which should be improved.
> 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. :-)
>
> 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.)
>
> 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 would suggest this:
1. releease beta1 (in 2 weeks or so)
2. focus on improving English strings, fix all strings that are ambiguous or
hard to understand
3. string freeze, release beta2, ping the original translators
4. beta3 should be fully translated
Vladimir
------------------------------------------------------------------------------
_______________________________________________
Geeqie-devel mailing list
Geeqie-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geeqie-devel
