hi,

bit of background:
my system is setup to use C/en as default (there are few things i hate
more than localized compiler errors).
however some desktop applications (most noteably: gramps) i'd like to
run in german.

On 04/03/2014 02:31 PM, Ross Gammon wrote:
> 
> I have come across similar problems before. I believe that Gramps does
> not support non-UTF-8 locales. 

i sincerely hope that i got rid of all non-utf8 locales a long time ago.

however,...

> If you start with "LANG=de", gramps
> will default to the "C" locale.
> 
> Could you try?:
> $ LANG=de_DE.UTF-8 gramps
> 

did that (and also tried `LANG=de_AT.UTF-8 gramps` which is the actual
locale i'm trying to use) to no avail.

however, while doing so, i noticed that (after a recent re-installation
of the entire system) the only locale i had configured on my system was
en_US.UTF-8.
building de_AT.UTF-8 did not help.

then i dug into gramps a little bit, and noticed that "-v" should print
out (among other things) the currently used locale:

$ locale
LANG=en_US.utf8
LANGUAGE=en_US:en
...
LC_ALL=

$ LANG=de_AT.UTF-8 /usr/bin/gramps -v
...
Environment settings:
---------------------
 LANG      : en_US.UTF-8
 LANGUAGE  : en:en
 GRAMPSI18N: not set
 GRAMPSHOME: not set
 GRAMPSDIR : not set
...

# so i tried using LANGUAGE instead:

$ LANGUAGE=de /usr/bin/gramps -v
...
Environment settings:
---------------------
 LANG      : de_DE.UTF-8
 LANGUAGE  : de
 GRAMPSI18N: not set
 GRAMPSHOME: not set
 GRAMPSDIR : not set
 PYTHONPATH:
...

# that looked promising!

$ LANGUAGE=de /usr/bin/gramps

# gives me a german gramps!

i'm sure it did work wit LANG previously.
anyhow, i'll adapt my scripts to use LANGUAGE now.


mdar
IOhannes

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to