Re: [Bug-gnubg] Untranslated items

[Petr Kadlec]

Well, I take back what I have said, being now completely confused. As I 
wanted to look at the GTK name of the font (btw, according to GIMP, it is 
"-unknown-OCR A Extended-normal-r-normal--18-135-96-96-m-0-iso8859-1"), I 
have installed it once again. And now..., everything works fine. :-o As I 
see it, everything is completely identical to the original situation (the 
font is installed, no gtkrc whatsoever), yet, now everything has correct 
charset, gnubg now uses Lucida Console, which is correct. So, forget about 
all the charset problems, please; if I would ever find some logic in it, I 
will report it, but until then, let's blame the sunspots...

> What I don't like about a list with "language, translator(s)" is that we
> would have to maintain it :-)

My idea was not to have a list of translators, but just a single line in 
the about box, indicating only the translator of the CURRENTLY used 
translation, so that the user would not need to search some readme file for 
the translation author if he/she wants to report a translation bug. If I 
"translate" the message "With special thanks to:" to something like "Czech 
translation: Petr Kadlec <address@hidden>\nWith special thanks to:", 
it would mean no further work to anyone. The question is whether it is 
acceptable to "overload" the message that way.
But some generic line like "Translation bugreports should go to 
address@hidden" is of course also fine.

Petr Kadlec

-- -----------------------------------------------------------
If it ain't broke, don't fix it. - Ronald Reagan