[Freeciv-Dev] Re: Mac OS X

[Nathan Brazil <nb@xxxxxxxxxxxxxxx>]

Okay.  So I've got Freeciv to build with NLS support.  However, I am  
seeing some issues:
1.  --enable-nls seems to be incompatible with libreadline, as I've  
had to also specify --without-readline in order to compile, at least  
on Mac OS X.  Has anyone else seen this?
2. Many of the translations seem ... incomplete.  That is, while some  
text might appear in the native languages, many still appear as  
English.  Is this just the current state of these translations?
3. I can get most Roman languages to work, but I cannot seem to get  
Japanese to work.  Is there some issue w/ Unicode, or is it just my  
system?
On Jul 7, 2005, at 10:25 AM, Jason Dorje Short wrote:

> On 7/7/05, Nathan Brazil <nb@xxxxxxxxxxxxxxx> wrote:
>
>
> > In any case, I've played around language support only a little bit,
> > and the results thus far aren't promising.
> >
> > For instance, if I manually invoke the game client after setting the
> > LANG environment variable to de, a few elements would change, most of
> > the game remains in English.  In fact, whenever I try to run
> > civclient with the LANG environment variable set to some value, I get
> > the following warning message:
> >
> > (civclient:672): Gtk-WARNING **: Locale not supported by C library.
> >          Using the fallback 'C' locale.
> >
> > To be honest, I am not sure why it is not working.  My packages are
> > built with the --with-included-gettext and --disable-nls flags.  Do
> > these settings affect localization any?
> Heh heh.  --with-included-gettext isn't recommended, and --disable-nls
> will disable translation entirely.  You need --enable-nls.
>
> If that still doesn't work, check if you can get other applications to
> work in the language.  Running in a different language requires more
> than just setting $LANG; you also have to configure your system to
> support that language.  On my debian/linux system I have to run
> "dpkg-reconfigure locales" and choose which locales I want to enable.
>
> Also note that many strings are provided by GTK not by freeciv.  GTK
> of course does its own translation of these texts (and some pictures
> too) based on your $LANG.  The important point here is it's possible
> to get GTK texts to be translated even if freeciv translations don't
> work.
>
> -jason