[Top][All Lists]

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

[Bug-gnubg] i18n-related issues

From: Petr Kadlec
Subject: [Bug-gnubg] i18n-related issues
Date: Wed, 21 Apr 2004 23:28:42 +0200

Hi all!

I've just commited changes in several files -- mainly added some missing calls to gettext, plus fixed a few typos on the way. I hope I didn't broke anything, because I had quite hard time making cvs work on my machine... (and this is my first commit to gnubg -- wow!) ;-)

I just wanted to ask translators to check/update their translations to reflect the added/modified items.

And one additional question: in gtkprefs.c, there are the following lines:

char* pieceTypeStr[NUM_PIECE_TYPES] = {N_("Rounded disc"), N_("Flat edged disc")}; char* textureTypeStr[NUM_TEXTURE_TYPES] = {N_("Top only"), N_("All of piece")};

The strings are marked as translatable, but they are not given to gettext anywhere. I thought I'll fix that, but I've noticed that those strings are not only presented to the user, but also compared (via strcmp) with the user-selected text that comes somehow through GTK (sorry for the fuzzy terminology, I don't know how GTK works). So I was afraid to mess with that. Could someone please explain to me if it is OK to just wrap any occurrence of {piece|texture}TypeStr to gettext (even in that strcmp), or if there is some other mechanism to let the strings translate? (Or, maybe, just doing the required changes would be easier than trying to explain GTK to me. :-) )


As far as we know, our computer has never had an undetected error. - Weisert

reply via email to

[Prev in Thread] Current Thread [Next in Thread]