[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: How to set up multilingual OO (including arabic?)



Hi Chris,
maybe I need another hint to some obvious things. :^)

On Thu, Oct 23, 2003 at 09:25:15AM +0200, Chris Halls wrote:
> On Wed, 2003-10-22 at 18:32, Johannes Graumann wrote:
> > > Am running Debian Sid and have installed their 1.1.0-1, including
> > > several language support packages for my polyglot wife. Now I am at a
> > > loss of how to make ooffice work such that she can choose between
> > > Arabic, Spanish, Turkish, French, German or English at startup. I have
> > > searched the google archives for this but haven't come across anything
> > > ...
> 
> But you didn't look in README.Debian...
> 
> Language support
> ================
> You can get foreign language support by installing the
> openoffice.org-l10n-<lang> package for your language.  You will also
> need the
> 'locales' package installed.  The user interface language is selected
> according
> to your locale(1) settings.
> 
> To change the user interface language for all users, run
> 
>   dpkg-reconfigure locales
> 
> To change the language for just one user, you must arrange for the
> LC_MESSAGES
> or LANG environment variable to be set.  You can list all available
> locales
> with the command 'locale -a'.
> 
> For example, to run OpenOffice in German from the command line:
> 
>   LANG=de_DE openoffice

This works fine from the shell, where I can set the appropriate
environment variables (LANG, LC_ALL).
The problem arises in kde, when OOo is invoked from a menu. This
obviously does not honor the user settings and thus OOo sets LOCALEOO to the
default of en-US.

I can change this by creating the file /etc/openoffice1.1/openoffice.conf
(which is read by the wrapper script /usr/bin/openoffice1.1) and putting
LANG=de_DE@euro (example) into it.

But this is no real solution as it changes systemwide to another
default.

The user locale settings are honoured when I change the first line of
/usr/bin/openoffice1.1 to

   #!/bin/bash --login

This reads in the user environment, which #!/bin/sh doesn't.
I don't expect this to be a clean solution.

BTW, the same problem appears with the user setting of umask. I have a
umask of 007 on shell level but OOo creates files with -rw-r--r--.

Any solution?

Helmut

-- 
--------------------------------------------------------------------
 Helmut Lichtenberg    <heli@tzv.fal.de>   Tel. +49 (0)5034/871-128
 Institut für Tierzucht           31535 Neustadt            Germany
--------------------------------------------------------------------



Reply to: