[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-gnubg] Translation issues again
From: |
Joern Thyssen |
Subject: |
Re: [Bug-gnubg] Translation issues again |
Date: |
Sun, 30 Nov 2003 09:24:02 +0000 |
User-agent: |
Mutt/1.4.1i |
On Tue, Nov 25, 2003 at 11:25:10AM +0100, Petr Kadlec wrote
> Hi all, it's me again...
>
[snip]
> As it seems to me, the problem may be caused by the fact, that some of the
> font names have iso8859-1 hardcoded, so that gtkrc does not affect them, or
> am I wrong? Wouldn't it solve the problem if those iso8859-1 were changed
> to * ?
Yes, you're probably right.
>
> If that is the case, I would also ask to search the source for all
> "iso8859-1" (and "iso-8859-1") strings and change them to either "*" in the
> case of GTK fonts,
I've "s/iso8859-1/*/g" in the GTK fonts.
> or let them be configurable, as in the case of HTML
> export, where <meta http-equiv="Content-Type" content="text/html;
> charset=ISO-8859-1" /> is always output, no matter what language+charset
> gnubg uses. The simplest solution is IMHO to use gettext on that
> "ISO-8859-1" string, which allows the translator to change it to whatever
> charset he/she uses.
Yes, but that won't work.
Internally gnubg stores texts in UTF-8 (or ISO-8859-1, depending on
GTK+, OS, and other configure options). Text destined for the terminal
is converted to the terminal charset.
I'm in the process of modifying the HTML expoert code for a more general
solution.
Jørn
pgp7cigBT7awO.pgp
Description: PGP signature