Complete.Org: Mailing Lists: Archives: freeciv-dev: December 2004:
[Freeciv-Dev] Re: (PR#11286) Invalid string conversion from UTF-8 to ISO
Home

[Freeciv-Dev] Re: (PR#11286) Invalid string conversion from UTF-8 to ISO

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: chrisk@xxxxxxxxx
Subject: [Freeciv-Dev] Re: (PR#11286) Invalid string conversion from UTF-8 to ISO-8859-15
From: "Jason Short" <jdorje@xxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 1 Dec 2004 14:09:10 -0800
Reply-to: rt@xxxxxxxxxxx

<URL: http://rt.freeciv.org/Ticket/Display.html?id=11286 >

Christian Knoke wrote:

>>Also, the GTK+ 1.2 client is mostly unmaintained, 2.x will most
>>likely be better.
> 
> Hhm, yes. But what to do with GTK1? A plus is it is quite good debugged,
> other than GTK2. And GTK2 has still some drawbacks in the GUI; it will take
> some time to make it fit. To drop GTK1 now is a pity.

PR#10971 uses transliteration, which should allow the gtk1 and xaw 
clients to work okay and should let the win32 client work very well.

(The win32 client is probably always compiled with GNU libiconv which 
has good transliteration.  Gtk1 and xaw clients are usually compiled 
with glibc iconv which has rather mediocre transliteration.  So 
Władyslaw may be transliterated as Wladyslaw with GNU libiconv but will 
be transliterated as W?adyslaw in glibc iconv.)

A long-term solution to this problem may be to make the nation names 
ascii and have them be translated.  This puts a huge burden on the 
translator but allows things to work for everyone (e.g., Japanese nation 
names can be translated into Japenese for ja_JP language).  It *might* 
be possible to use UTF-8 in translated strings but this will only work 
if all the .po files also use UTF-8.

-jason





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