Complete.Org: Mailing Lists: Archives: freeciv-dev: January 2003:
[Freeciv-Dev] Re: (PR#2374) multi-language client-server patch
Home

[Freeciv-Dev] Re: (PR#2374) multi-language client-server patch

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
Cc: freeciv-dev@xxxxxxxxxxx
Subject: [Freeciv-Dev] Re: (PR#2374) multi-language client-server patch
From: "mateusz stefek via RT" <rt@xxxxxxxxxxxxxx>
Date: Thu, 23 Jan 2003 23:53:30 -0800
Reply-to: rt@xxxxxxxxxxxxxx

Dnia 2003.01.23 23:07 Jason Short via RT napisa³(a):
> mateusz stefek via RT wrote:
> > See incoming/fims.tgz
> >
> > I've spent many hours writing and testing it, so have fun
> 
> Ok, one more final question...
> 
> It has been pointed out that you could translate into the client's
> locale at the server end.  That is, the client could send the server
> their $LANG and the server could translate directly into that
> language.
> 
> The disadvantage of this is that the server must not only be
> configured
> for NLS, but must have all possible locales configured.  If the client
> 
> wants pl_PL.UTF-8 but all you have is pl_PL.ISO8859-2, no usable
> translation is possible (at least not without more work).
> 
> The advantage, though, is that only the server needs to have
> up-to-date
> translations.  For instance if a modpack is used the client will
> generally not have good translations of the modpack-specific strings -
> 
> but presumably the server would.
> 
> Is this accurate?  Are there any other considerations here?
> 

There is one problem,
How can you tell gettext that you wan't to use other language?
dcgettext isn't good enough for this.
I think that the only solution is to use included and patched gettext.

> jason
> 
--
mateusz



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