[Freeciv-Dev] Re: main map have gtk1.2 font problem (i18n) (PR#1606)

[Vasco Alexandre Da Silva Costa <vasc@xxxxxxxxxxxxxx>]

On Mon, 24 Jun 2002, SAWADA Katsuya wrote:

> Vasco Alexandre Da Silva Costa <vasc@xxxxxxxxxxxxxx> writes:
> > On Sat, 22 Jun 2002, SAWADA Katsuya wrote:

> I compiled client with GTK+ 2.0, and tested the client.
> I couldn't read messages in japanese expect GTK+ 2.0 themselevs
> messages "_Quit" and "_Jump to" on connection dialog.
>
> The problem looks like character encoding.
> I (and mostly 100% Japanese) am using LANG=ja_JP.eucJP, but Pango
> looks take only UTF-8 encoding.

Yes. You are correct. Pango must have UTF-8 as input.

> I executed civclient with LANG=ja_JP.UTF-8, then it works good.  Now I
> can read Japanese message on the dialog. But, client also output UTF-8
> character to terminal emulator. It is not important to read console
> message, but problem.

There are versions of XTerm that support UTF-8:
<http://dickey.his.com/xterm/>
<http://www.debian.or.jp/~kubota/xterm.html>

I will try to make the client work with EUC-JP. Could you please post a
screenshot of how the client looks with the EUC-JP locale somewhere?

> Here is what I can't read.
> 1: Cannot find audio spec-file "stdsounds.spec".
> 1: To get sound you need to download a sound set!
> 1: Get sound sets from <ftp://ftp.freeciv.org/freeciv/contrib/sounds/sets>.
> 1: Will continue with disabled sounds.
>
>
>
> I'm thinking two models to solve this problem.
>
> Terminal encoding: You like encoding
>  Freeciv Internal: UTF-8
>   Pango, Gtk+ 2.0: UTF-8
>
> or
>
> Terminal encoding: You like encoding
>  Freeciv Internal: You like encoding
>   Pango, Gtk+ 2.0: UTF-8
>
>
> First model do translate to UTF-8 when program call gettext.  Message
> is passed to Pange without change. When program output to terminal,
> message was translate to their own encoding from UTF-8.
> Problem is we have to think about where to messages should go.
>       fprintf(stderr, _("Unrecognized option: \"%s\"\n"), argv[i]);
> don't need translate to UTF-8. Same problem has freelog. So we may
> need to have special macro like N_, and change many source code.

It is a problem that gettext only supports one locale.

> Second model do translate to UTF-8 when message pass to Pango.
> I feel it is simple.
>
> I lack of knowledge Freeciv core code especially client-server packet,
> so it is not sure.  But, I suppose first model is good because Freeciv
> use client-server model and first model is we can connect same server
> with various client using each language.

Yes that was my idea. To eventually make all the clients use UTF-8 for
transmitting over the network. Things still are pretty much broken for
anything other than ISO-8859-1 when transmiting strings over the network.
In fact, the GTK+ 2.0 client passes network strings in ISO-8859-1...
If it didn't it wouldn't work with the other clients as they are now.

In short, I am thinking about using your first model. Unfortunately
console output on the client is not the single problem.
There still is the matter of the portability of savegames on the server
and several others.

I will see if i can fix the problems with console output.

---
Vasco Alexandre da Silva Costa @ Instituto Superior Tecnico, Lisboa