PDA

View Full Version : OpenOffice 1.1.1 starts & installs in German on English



Craig2
05-08-2004, 12:52 AM
I've tried running OpenOffice 1.1.1 on the English Knoppix CD (May 04 version). As Knoppix user, it starts the installation script in German, offering no option for English. Once installed, I've tried changing the language (for documents?) to English, and that doesn't work. I'm installing the local (non-network) install.

I tried running it as a different user on my system, and it still installs and runs in German.

I've tried editing the configuration files on a previous install (1.0.4?), when I had this problem before on an earlier Knoppix disk, editing the language codes everywhere in the config file to English, but that didn't help. I also posted about this for the earlier release, but didn't get an answer.

Any ideas? Is every English speaker running Knoppix using OpenOffice in German from the live cd?

I'm running knoppix from the live cd, not from hard disk, so an apt-get solution won't work for me.

Craig2
05-11-2004, 05:03 AM
Anyone else having this problem?

Anyone have a solution?

user unknown
05-11-2004, 05:19 AM
can you test in the console and report:

echo $LANG
echo $LC_ALL
echo $COUNTRY

and

env | grep de
env | grep DE

Craig2
05-11-2004, 06:07 AM
can you test in the console and report:

echo $LANG
echo $LC_ALL
echo $COUNTRY

and

env | grep de
env | grep DE

$ echo $LANG
C

$ echo $LC_ALL
C

$ echo $COUNTRY
us

$ env | grep de
GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/knoppix/.gtkrc-2.0:/ramdisk/home/knoppix /.kde/share/config/gtkrc
GTK_RC_FILES=/etc/gtk/gtkrc:/home/knoppix/.gtkrc:/ramdisk/home/knoppix/.kde/sha re/config/gtkrc
XCURSOR_THEME=default

$ env | grep de
GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/knoppix/.gtkrc-2.0:/ramdisk/home/knoppix/.kde/share/config/gtkrc
GTK_RC_FILES=/etc/gtk/gtkrc:/home/knoppix/.gtkrc:/ramdisk/home/knoppix/.kde/share/config/gtkrc
XCURSOR_THEME=default

knoppix@ttyp1[knoppix]$ env | grep DE
KDE_MULTIHEAD=false
KDE_FULL_SESSION=true
KDEDIR=/usr

craig2@ttyp1[craig2]$ echo $LANG
C

craig2@ttyp1[craig2]$ echo $LC_ALL
C

craig2@ttyp1[craig2]$ echo $COUNTRY
us

craig2@ttyp1[craig2]$ env | grep de
GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/knoppix/.gtkrc-2.0:/ramdisk/home/knoppix/.kde/share/config/gtkrc
GTK_RC_FILES=/etc/gtk/gtkrc:/home/knoppix/.gtkrc:/ramdisk/home/knoppix/.kde/share/config/gtkrc
XCURSOR_THEME=default

craig2@ttyp1[craig2]$ env | grep DE
KDE_MULTIHEAD=false
KDE_FULL_SESSION=true
KDEDIR=/usr

craig2 is a user from an older install, start and run by cd into /mnt/sda1/craig2/ and su'ing into craig2, then running apps from the command line while logged into the tty as craig2, all the dot configuration files from the old install are there, so everything has been working fine up until this problem with German OpenOffice. I believe the problem also existed in knoppix 3.3, while logged in as craig2, but running as knoppix the problem didn't exist, so I ran OOo as knoppix user, then changed ownership and permissions of data as necessary. I tried changing the country codes of OOo configuration files in craig2's install to US from German everywhere I found them, but it didn't work.

tia.

user unknown
05-11-2004, 07:01 AM
Well, I thought your system might be set up to german, but all what is setup is the Country to 'us' - while 'C' schould be fine for americans. ('de'='deutsch'='german')

So perhaps the OpenOffice-package is only bundled with german localisations.
Perhaps you find a solution at openoffice.org:
http://www.openoffice.org/

Craig2
05-11-2004, 08:00 AM
Thanks for your assistance anyway. It reminded me of some other areas (paths) that I need to review.

As for checking the OpenOffice site, I'm going to take a look at it, but I'm sure this is a knoppix issue, not an OOo issue. I have walked others through installing OOo and this problem doesn't exist on several different distros.

Thanks again.

champagnemojo
05-11-2004, 10:50 PM
Are you sure you got the English ISO? I've never had such a problem with OpenOffice in Knoppix.

j.drake
05-12-2004, 03:41 AM
Are you sure you got the English ISO? I've never had such a problem with OpenOffice in Knoppix.

No, Craig is absolutely right on this one. I noticed the same thing in the 2004-05-04 release, and it's still in the 2004-05-10 release. Two of the submenus in the File menu are in German (Auto-pilot and New), but all of the other menus appear to be in English. I have OpenOffice 1.1.1 for Windows, and all the file menus are in English. This is definitely a Knoppix issue, not an Open Office issue, and not something peculiar with Craig's setup.

JD

j.drake
05-12-2004, 03:46 AM
BTW, has anyone set up a bug page for 3.4 2004-05-10? The bug wiki only lists the 3.4 2004-05-04 version, and requests that we confine the bugs to that version only

JD

champagnemojo
05-12-2004, 03:54 AM
Just checking...the latest Kanotix does the same thing. It's an easy fix on an hd-install, but I guess you'll just have to learn some German if you have to run it live. :P

j.drake
05-12-2004, 04:19 AM
Well, fortunately "Textdokument" is something within my inferential capabilities, and I can guess at most of the rest, but I can't honestly say that I know what a Zeichnung is. :)

user unknown
05-12-2004, 01:04 PM
Zeichnung: drawing

http://dict.leo.org/

is a onlinedictionary which says: chart, diagram, painting, ...

Craig2
05-12-2004, 04:27 PM
can you test in the console and report:

echo $LANG
echo $LC_ALL
echo $COUNTRY

and

env | grep de
env | grep DE

Thanks to Knoppix, there are a lot of current and former windows users who are trying Debian/Gnu/Linux for the very first time. A big thanks goes out to Klaus, Probono, Fabian Franz, Christian Perle, and others who either have helped with Knoppix, or who take the time to explain how things work, and help newbies on the mailing list and in these forums. I'm not a techie. I simply like Gnu/Linux. I've been using it for a few years now, but I don't have the resources to have a box to experiment with. Every setup I've had up to and including now has been a recovery of something else, and ongoing attempts to hold on to data that I don't want to lose. So I haven't been able to get into the basics of how the systems really work.

I still consider myself a newbie. Until I build a system using Linux From Scratch, get some better experience with Debian, build and use another system from slackware, get to know the command line better, get to know shell scripting better (or at least start), and get to know other areas better, I'll always consider myself a newbie. From a newbie's point of view, I'd like to point out the following for the more experienced users out there offering help on the mailing list and in these forums:

Just as you have learned html, scripting, and other areas by copying, so do we. The person who asked for me to check a few settings above, and others who ask us to do the same, please remember this: It will be very helpful for you to also include a few sentences as to what exactly it is that you are asking us to look for. As a further example, for those of you familiar with Suse's Yast configuration tool, Yast is a great configuration tool. Thanks to that tool, in the past, I was able to keep systems running without any problems, including file servers, web servers, nis servers, nfs servers, and more. But I always had trouble understanding exactly what the tool was doing. It was obviously running scripts according to my entries, but that was behind the scenes. While I could have, and should have, taken the time to learn each step of what I was doing with the entries, nothing would beat actually showing the command line entries, and shell scripts in action, as the entries were made. There should have been an option that allowed me to see the resulting command line entries that were run each time I pressed the "enter" or "apply" button. Note that this is not a criticism. By telling us why we are doing what you ask, and what it is exactly that we are doing, you are helping us to learn, and helping us to help others when the time comes.

This problem with OpenOffice is similar. I know it's a German switch, flag, or file that is triggering the installation to install in German. I also know I should be checking paths, but I can't remember how to do that right now.

What I have discovered, is that in the user directories that are not knoppix user (craig2 for example), I have a lot of dot configuration directories and files that have "de" on the top line or near the top line of each file, with other languages below them. Some files end in dot desktop ".desktop" and there are others. I've changed some to "en" where I see "de", and others I've either rm'd or I've mv'd them to a backup file. I'd like to erase all of them, but I'm aware that OpenOffice stores some user data within its own directories, instead of the user's Documents directory, and I don't want to lose data. So what I've done instead is to move the directories into backup directories, so that there are no OpenOffice dot directories anymore in the user's directories. Since I've been using Knoppix for a while, I have Directories for OpenOffice641, OpenOffice1.0.3, OpenOffice 1.1.0, and OpenOffice1.1.1 Those have all been moved to backup directories.

I've also discovered that in /etc, I have the following file:

24 May 12 06:15 language-de -> /KNOPPIX/etc/language-de

and the file contains:

# #!/bin/sh -- This should not be executed, but sourced.
# This file was installed by the package user-de and contains the
# settings for German speaking users

# If you just want Umlauts and accents (also in Mutt), but all the
# messages in English then uncomment the following entry.
#LC_MESSAGES=en_GB.UTF-8
#export LC_MESSAGES

# This sets the locale to German/Germany.
# You might want to try de_AT etc. instead
LANG=de_DE.UTF-8
export LANG
# If you want a German GNOME Desktop as well, you also have to set
# LANG=de_DE.UTF-8 in /etc/environment, which is a good idea anyway!!!

# If you should prefer English manpages
# then uncomment the following two lines.
#MANOPT='-L english'
#export MANOPT


# A couple of programs use this as a default for the MIME charset.
MM_CHARSET=UTF-8
export MM_CHARSET
__________________________________________________ __

I know that the above is wrong. I rebooted, so that would explain today's date. So what file should I have there instead? I believe I should have one that is language-en instead, correct? Should I delete this file?

Just to answer another question, this is the disk I'm running:

knoppix@ttyp4[lr15]$ ls
KNOPPIX_V3.4-2004-05-04-EN
knoppix@ttyp4[lr15]$ cd KNOPPIX_V3.4-2004-05-04-EN/
knoppix@ttyp4[KNOPPIX_V3.4-2004-05-04-EN]$ ls
KNOPPIX-CHANGELOG.txt KNOPPIX_V3.4-2004-05-04-EN.iso.md5 knoppix-cheatcodes.txt
KNOPPIX_V3.4-2004-05-04-EN.iso KNOPPIX_V3.4-2004-05-04-EN.iso.md5.asc packages.txt
knoppix@ttyp4[KNOPPIX_V3.4-2004-05-04-EN]$

And I of course checked the md5sum, even though bittorrent does that as well.

Can someone who knows better what he or she is doing, who is having the same problem with languages in OOo, do a search for any files which have "de" in them, possibly separated from other letters with a - or _ or other non letter character, and see if this is the problem?

The Textdokument or whatever someone else reported was seen by me in Knoppix 3.3 also, and possibly earlier versions as well, but since I could figure out that it was for text documents, it was still usable. There were other problems in other menus as well, but the office suite was mostly installed as English, and it was usable. Something happened with 3.4 that wasn't happening in 3.3 and earlier releases, although in 3.3 I still had a German (complete) install in user craig2, but knoppix user installed in English, so I could still use the suite, even though Textdokument, and a few other menu items were in German.

user unknown
05-12-2004, 05:01 PM
When I try to help someone to solve a problem, I'm sometimes detailed, and sometimes really short. I might be tired or simply lazy, but of course I never know how much the user already knows.
I assume at least that the user knows 'man, whatis, apropos'.
Well - in your case it might not be very useful, since the manpath points to german manuals. :)

env shows a lot of your settings, such as LANGUAGE.
grep searches for a token - in this case for 'de'. DE isn't as popular as US, but since the question was about the german language, I thought you might get this on your own.

I guess I better reply shortly than not at all.
---
I don't feel competent to solve your problem.
Running linux for 8 years now, I always had problems with language- and locale-settings.
I switched from distro to distro, from suse to redhat, to halloween and to peanut and knoppix - and setting up the keyboard and the fonts for the console and for X11 was mostly problematic and not completly solvable, though reading lots of manuals, leading from here to there and back again -
everyone was using a different solution so I gave up.
Now, this knoppix-release worked out of the box - but since I use german, I may not tell you how to switch away.

Perhaps there is a bootoption lang=en_US or similar?

Craig2
05-12-2004, 05:21 PM
When I try to help someone to solve a problem, I'm sometimes detailed, and sometimes really short. I might be tired or simply lazy, but of course I never know how much the user already knows.
I assume at least that the user knows 'man, whatis, apropos'.
Well - in your case it might not be very useful, since the manpath points to german manuals. :)
<snip>
I guess I better reply shortly than not at all.
---
<snip>
Perhaps there is a bootoption lang=en_US or similar?

As I stated, it wasn't meant personally. Your help was definitely appreciated, and pointed to some other areas that I needed to refresh myself on, and areas that other newbies should study on. I simply took the opportunity to point out a more appreciated way of answering a question for newbies to learn on. Often, list posts are terse, and don't explain why someone is asking what they're asking, or what effect the resulting entry would have, etc. I just posted the response as a reminder that we like to, and need to, learn while we are doing, and the best way for that is to understand ourselves what it is you are trying to find out in order to answer the question. That's it, nothing more. Due to fatigue, and a thousand other reasons, this isn't done all the time, nor can it. But a friendly reminder asking to do this is good, don't you think?

I'm going to try rebooting with the lang=US flag. I already have this in my saved configuration, but it may make a difference for OOo. I'll add it to knoppix myconfig=/dev/hda1 dma flag that I use to boot.

I also tried rm'ing the OpenOffice directory in my home directory, then running soffice again. It popped up an error message telling me the installation was broken, did I want to repair it. I clicked yes, and then was presented with the registration box written in German. I declined registration, and OOo started in German. So that didnt' work.

I've been looking at the /usr/bin/soffice file. I've been trying to get hints where it looks for Language or locale settings, but it seems to be correct. I'm wondering if I can edit the file as a workaround, and force it to en-US directly in the script, instead of the script checking locales/lang in other directories. Is this possible?

This is the the installation script I have (the whole thing doesn't fit, this is from /usr/bin/soffice):

#!/bin/bash
PROGRAM_PATH=/opt/openoffice/program
CHECKMEM=""

# Show logo in background
SCREEN="$(xdpyinfo | awk '/dimensions/{print $2; exit 0}')"
X="$(expr ${SCREEN%%x*} / 2 - 235)"
Y="$(expr ${SCREEN##*x} / 2 - 160)"

# Quick visual feedback
xloadimage -quiet -geometry 0x0+$X+$Y -delay 140 /opt/openoffice/program/soffice-startup.gif >/dev/null 2>&1 &
xpid="$!"

[ -x /usr/bin/checkmem ] && CHECKMEM="/usr/bin/checkmem 80"

# Language/Locale settings
[ -z "$LANG" -a -e /etc/sysconfig/i18n ] && . /etc/sysconfig/i18n
export LANG
USELANGUAGE="${LANG%%@*}"
USELANGUAGE="${USELANGUAGE%%_*}"
case "$USELANGUAGE" in
de|ch|at)
USELOCALE=de-DE
;;
nl)
USELOCALE=nl-NL
;;
C)

user unknown
05-12-2004, 05:47 PM
It might work or not work.

I thought you were allways running from cd?

It looks as if the installer is reading it's settings from /etc/sysconfig/i18n so you should print it to the screen:



cat /etc/sysconfig/i18n

# my output:
#
LANG="de_DE@euro"
COUNTRY="de"
LANGUAGE="de"
CHARSET="iso8859-15"
XMODIFIERS=""

# yours should probably look like this:
LANG="en_US"
COUNTRY="us"
LANGUAGE="us"
CHARSET="iso8859-1"
XMODIFIERS=""


but I'm not sure, whether the installer will FIND apropriate en_US - files to install.

And note: I'm not sure about the boot-option, whether it is 'LOCALE=...' or 'LANG...' or something similar, but the help-screen should mention some option.

Craig2
05-12-2004, 06:17 PM
knoppix@ttyp9[knoppix]$ cat /etc/sysconfig/i18n
LANG="C"
COUNTRY="us"
LANG="C"
LANGUAGE="us"
CHARSET="iso8859-1"
XMODIFIERS=""
knoppix@ttyp9[knoppix]$

I looked at this just a little while ago. Don't know what Lang="C" is, but when I saw COUNTRY="us" and LANGUAGE="US", I figured it was ok. Maybe C is canadian. if canadian english is the setting, that's certainly better than German, and something I can live with. I'd change it, but should it be US? or us?...and so on.

So if someone has a working install of OpenOffice.org in US English, and has a knoppix 3.4 English CD, I'd be interested in what your $ cat /etc/sysconfig/i18n reports.

Yes, I'm running from CD. But I can edit /etc and other directories because I have a persistant home. As for editing the script, don't know if I can, but checking the location, it doesn't appear to be a link from the cd, so I should be able to edit it.

Craig2
05-12-2004, 06:34 PM
Yes, I'm running from CD. But I can edit /etc and other directories because I have a persistant home. As for editing the script, don't know if I can, but checking the location, it doesn't appear to be a link from the cd, so I should be able to edit it.

Let me correct myself before someone else does. Persistant home has nothing to do with editing /etc. Kick myself for that one. Anyway... I can edit some files in some directories because I working from an underlying installation of a different distro, and working from the ramdisk. If I understand it correctly, I can edit /etc because /etc is in my ramdisk, and as long as I save my configuration after the edits, I can edit /etc files and it works. As for data, I can save knoppix user's data in /home/knoppix, but then I have to save the configuration file. I have a couple of other users, one is craig2, and when running applications as craig2, I don't have to save my configurations for craig2 because craig2's home is on a partition on my hard disk, not on a ramdisk. I also have on the same partition, a directory for knoppix2, where I can save data to for knoppix, and not have to worry about remembering to save my configuration or risk losing the data. That doesn't help with configuration files which are automatically saved in /home/knoppix on the ramdisk though.

Hope that helps for an understanding of my setup.

The soffice script, I'm assuming, has been placed into /usr/bin, on the ramdisk, during startup. So I should be able to edit it, save the configuration, and it should work.

And for other newbies out there, when planning on editing files, before you start, do a ls -l, so you can see if the file is actually a link to a file on the cd, instead of on the ramdisk. If it is on the cd, you can't edit it. A workaround is to copy the file to the ramdisk from the cd, in the correct directory, removing the link. Then save the configuration, see if it still works (backup the link), then edit away, then save the configuration again. Should work.

pstoddard
05-12-2004, 06:54 PM
I had the same problem and I just uninstalled OOo that came with the disk and installed a fresh copy downloaded from OOo's web site.

Seemed to fix it for me and I still have launch capabilities from the K menu.

Craig2
05-12-2004, 07:08 PM
I had the same problem and I just uninstalled OOo that came with the disk and installed a fresh copy downloaded from OOo's web site.

Seemed to fix it for me and I still have launch capabilities from the K menu.

This won't work for people running from the CD. And if there's a klik recipe for OOo, that will give all the benefits, but also all the drawbacks, of that different setup (everything in a single user's home directory, instead of in the different directories such as /usr/bin and using the libraries and everything else from the original install. This prevents additional users, unless those users also install OpenOffice into their own directories as well (double disk space). Not normally an issue with a live cd, but with knoppix user, quite a few people with single user systems have an additional user as themselves. This also brings to mind problems with out of memory warnings, due to the large size of OpenOffice, if its downloaded as a klik recipe on a live cd setup (check the forums, I won't go into the details of the out of memory warnings, though I had one myself and I have 512 MB Ram and 2 Gigs of swap, with the ramdisk able to fully use the 2 Gigs of swap).

user unknown
05-13-2004, 02:56 AM
LANG='C' isn't canadian, which is 'en_CA' or 'fr_CA'.
C is the special exception and means the language of the programming language C - greetings to Kerninghan & Ritchie at this point - AFAIK, since their language is the default OS language, which should be 'en_US'. But again not sure.

If someones manpages are broken, here is a link to online-manpages:

http://www.rt.com/man/

Craig2: are you waiting on some kind of ok?
I would try it this way.

Craig2
05-13-2004, 03:23 AM
LANG='C' isn't canadian, which is 'en_CA' or 'fr_CA'.
C is the special exception and means the language of the programming language C - greetings to Kerninghan & Ritchie at this point - AFAIK, since their language is the default OS language, which should be 'en_US'. But again not sure.

If someones manpages are broken, here is a link to online-manpages:

http://www.rt.com/man/

Craig2: are you waiting on some kind of ok?
I would try it this way.

I must have missed something. Or forgot what I was doing. What should I be trying?

I stopped for a while, and forgot where I was. I have this file open:

#!/bin/bash
PROGRAM_PATH=/opt/openoffice/program
CHECKMEM=""

# Show logo in background
SCREEN="$(xdpyinfo | awk '/dimensions/{print $2; exit 0}')"
X="$(expr ${SCREEN%%x*} / 2 - 235)"
Y="$(expr ${SCREEN##*x} / 2 - 160)"

# Quick visual feedback
xloadimage -quiet -geometry 0x0+$X+$Y -delay 140 /opt/openoffice/program/soffice-startup.gif >/dev/null 2>&1 &
xpid="$!"

[ -x /usr/bin/checkmem ] && CHECKMEM="/usr/bin/checkmem 80"

# Language/Locale settings
[ -z "$LANG" -a -e /etc/sysconfig/i18n ] && . /etc/sysconfig/i18n
export LANG
USELANGUAGE="${LANG%%@*}"
USELANGUAGE="${USELANGUAGE%%_*}"
case "$USELANGUAGE" in
de|ch|at)
USELOCALE=de-DE
;;
nl)
USELOCALE=nl-NL
;;
C)

And suspect that the USELOCALE=de-DE and USELOCALE=nl-NL may have something to do with the problem, but again, I could be wrong. I can't remember where this file came from when I opened it, so I'm going to look for it in a little while, or try and find which shell I used to run kwrite when I opened it, and check the bash history to see the name of the file.

If this file is the problem, can I just change the entry to USELOCALE=en-EN, and what do I do with the following 5 lines? Or the one above USELOCALE=de-DE? Anyone have this file with english settings that they can post for me to look at?

As for waiting, I really wasn't waiting. I spent a lot of time looking for other files or settings from my bash shell, and then I went through every setting and every applicaton in the kde desktop start menu that I could try to find a path or language setting that wasn't correct. Everything is correct from what I see. I've also been googling for hours trying to find something, but no luck there either. If I didn't think this would help someone else, I wouldn't waste any more time on this. I'll just use OpenOffice on Windows on someone else's computer for now, as much as it kills me to say that. In the next few weeks I'll have a hard disk install of Sarge, and it won't be an issue anymore, I'll be able to use apt to uninstall/install whatever necessary. I'll stop my post here because what I was going to write next was going to be out of sheer frustration.

Craig2
05-13-2004, 03:38 AM
btw, my man pages are in english, for both the knoppix user, and craig2. In an earlier post, someoone (my friend in Berlin?) said that the man pages would be useless to me because they're in German. They are not, they are English.

I'm not having a problem with anything else that I can think of regarding language. Just OOo.

And a reminder, the file I found in /etc, called language-de, and having the following inside:

# #!/bin/sh -- This should not be executed, but sourced.
# This file was installed by the package user-de and contains the
# settings for German speaking users

# If you just want Umlauts and accents (also in Mutt), but all the
# messages in English then uncomment the following entry.
#LC_MESSAGES=en_GB.UTF-8
#export LC_MESSAGES

# This sets the locale to German/Germany.
# You might want to try de_AT etc. instead
LANG=de_DE.UTF-8
export LANG
# If you want a German GNOME Desktop as well, you also have to set
# LANG=de_DE.UTF-8 in /etc/environment, which is a good idea anyway!!!

# If you should prefer English manpages
# then uncomment the following two lines.
#MANOPT='-L english'
#export MANOPT

Anyone with the English settings inside, or a file called language-en in /etc and no language-de in /etc, can you post the exact name of file, and the contents, if you have a working OOo in English on Knoppix 3.4?

I tried a locate for language-en, but that came up empty.

I'm going to run an updatedb now, so I'm signing off for now.

tia.

user unknown
05-13-2004, 04:19 AM
# Language/Locale settings
[ -z "$LANG" -a -e /etc/sysconfig/i18n ] && . /etc/sysconfig/i18n
export LANG
USELANGUAGE="${LANG%%@*}"
USELANGUAGE="${USELANGUAGE%%_*}"
case "$USELANGUAGE" in
de|ch|at)
USELOCALE=de-DE
;;
nl)
USELOCALE=nl-NL
;;
C)


well - this script reads /etc/sysconfig/i18n.
We had that topic. Your settings seem to be fine.
The quote of the script ends, where it would be interesting.
Is there a 'USELOCALE' followed by the C) ?
And is there a section
en) following, with different content than the C) section?

Another idea: Your installation-program is invoked from a kde-menu?
Perhaps this is linked to a installation-script, and passing a parameter like 'LANG=de'...
I'm not running kde, so I can't search for the name of this menuentry, and for the location of the entry 'edit menu'.

Craig2
05-13-2004, 05:03 AM
Another idea: Your installation-program is invoked from a kde-menu?
Perhaps this is linked to a installation-script, and passing a parameter like 'LANG=de'...
I'm not running kde, so I can't search for the name of this menuentry, and for the location of the entry 'edit menu'.

I'll check the first part of your post in a few minutes. The installation program has been tried from the kde kicker panel the first time for knoppix user, was invoked the first time for craig2 from a bash shell while in craig2's home directory (where there were earlier OOo641, OOo1.0.3 and whatever else I listed earlier, dot configuration files). I also tried invoking from a shell with knoppix a second time after deleting the configuration file installed for 1.1.1 So it's installing in German whether from a kde icon on the kicker panel, or from a command line. I may have even tried installing from the start button, or applications button in the programs menu of kde. I may not, so I'm thinking of trying that now. Let me review the first part of your post first though.

Craig2
05-13-2004, 05:15 AM
ok, it was cut off because of the limit on posting length. I'll post the rest in a few entries:

export LANG
USELANGUAGE="${LANG%%@*}"
USELANGUAGE="${USELANGUAGE%%_*}"
case "$USELANGUAGE" in
de|ch|at)
USELOCALE=de-DE
;;
nl)
USELOCALE=nl-NL
;;
C)
USELOCALE=en-US
;;
*)
USELOCALE="${LANG%%@*}"
USELOCALE="${USELOCALE/_/-}"
[ -z "$USELOCALE" ] && USELOCALE="en-US"
USELANGUAGE="${USELOCALE%%-*}"
;;
esac

# Check if we ever started OpenOffice before. Call setup if not.
if [ ! -e "$HOME"/.sversionrc ]; then

AUTOSETUP=""
[ -f "$PROGRAM_PATH/autosetup.conf" ] && AUTOSETUP="-R:$PROGRAM_PATH/autosetup.conf"

# Call auto-setup
echo "Running OpenOffice for the first time: Calling auto-setup" >&2
$CHECKMEM "$PROGRAM_PATH"/setup $AUTOSETUP || exit 1

LOCALOFFICE=$(awk '/^OpenOffice\.org/{dir=substr($0,match($0,"file://")+7)}END{gsub(/[\n\r]/,"",dir);print dir}' $HOME/.sversionrc 2>/dev/null)

# Change language settings
# Partly adopted from the Debian OpenOffice.org-debian-files package
echo "Running OpenOffice for the first time: Setting up locales and dictionaries" >&2
mkdir -p "$LOCALOFFICE/user/registry/data/org/openoffice/Office"

# Kill registration wizard (license already axxepted with network install)
echo '<?xml version="1.0" encoding="UTF-8"?>
<oor:component-data xmlns:oor="http://openoffice.org/2001/registry" xmlns:xs="http://www.w3.org/2001/XMLSchema" oor:name="Common" oor:package="org.openoffice.Office">
<node oor:name="Internal">
<prop oor:name="CurrentTempURL" oor:type="xs:string">
<value/>
</prop>
</node>
<node oor:name="Help">
<node oor:name="Registration">
<prop oor:name="ReminderDate" oor:type="xs:string">
<value xsi:nil="true"/>
</prop>
<prop oor:name="RequestDialog" oor:type="xs:int">
<value>0</value>
</prop>
</node>
</node>
<node oor:name="Misc">
<prop oor:name="FirstRun" oor:type="xs:boolean">
<value>false</value>
</prop>
</node>
</oor:component-data>' > "$LOCALOFFICE/user/registry/data/org/openoffice/Office/Common.xcu"

# Locales
echo '<?xml version="1.0" encoding="UTF-8"?>
<oor:component-data xmlns:oor="http://openoffice.org/2001/registry" xmlns:xs="http://www.w3.org/2001/XMLSchema" oor:name="Linguistic" oor:package="org.openoffice.Office">
<node oor:name="SpellChecking">
<prop oor:name="IsSpellAuto" oor:type="xs:boolean">
<value>true</value>
</prop>
</node>
<node oor:name="ServiceManager">
<node oor:name="HyphenatorList">
<prop oor:name="de-DE" oor:op="replace" oor:type="xs:string">
<value>org.openoffice.lingu.LibHnjHyphenator</value>
</prop>
<prop oor:name="de-AT" oor:op="replace" oor:type="xs:string">
<value>org.openoffice.lingu.LibHnjHyphenator</value>
</prop>
<prop oor:name="en-US" oor:op="replace" oor:type="xs:string">
<value>org.openoffice.lingu.LibHnjHyphenator</value>
</prop>
<prop oor:name="nl-NL" oor:op="replace" oor:type="xs:string">
<value>org.openoffice.lingu.LibHnjHyphenator</value>
</prop>
</node>
<node oor:name="LastFoundHyphenators">
<prop oor:name="de-DE" oor:op="replace" oor:type="oor:string-list">
<value>org.openoffice.lingu.LibHnjHyphenator</value>
</prop>
<prop oor:name="de-AT" oor:op="replace" oor:type="oor:string-list">
<value>org.openoffice.lingu.LibHnjHyphenator</value>
</prop>
<prop oor:name="en-US" oor:op="replace" oor:type="oor:string-list">
<value>org.openoffice.lingu.LibHnjHyphenator</value>
</prop>
<prop oor:name="nl-NL" oor:op="replace" oor:type="oor:string-list">
<value>org.openoffice.lingu.LibHnjHyphenator</value>
</prop>
</node>
<node oor:name="LastFoundSpellCheckers">
<prop oor:name="de-DE" oor:op="replace" oor:type="oor:string-list">
<value>org.openoffice.lingu.MySpellSpellChecker</value>
</prop>
<prop oor:name="de-AT" oor:op="replace" oor:type="oor:string-list">
<value>org.openoffice.lingu.MySpellSpellChecker</value>
</prop>
<prop oor:name="en-US" oor:op="replace" oor:type="oor:string-list">
<value>org.openoffice.lingu.MySpellSpellChecker</value>
</prop>
<prop oor:name="it-IT" oor:op="replace" oor:type="oor:string-list">
<value>org.openoffice.lingu.MySpellSpellChecker</value>
</prop>
<prop oor:name="nl-BE" oor:op="replace" oor:type="oor:string-list">
<value>org.openoffice.lingu.MySpellSpellChecker</value>
</prop>
<prop oor:name="nl-NL" oor:op="replace" oor:type="oor:string-list">
<value>org.openoffice.lingu.MySpellSpellChecker</value>
</prop>
</node>
<node oor:name="LastFoundThesauri">
<prop oor:name="de-DE" oor:op="replace" oor:type="oor:string-list">
<value>org.openoffice.lingu.basic.Thesaurus</value>
</prop>
<prop oor:name="en-US" oor:op="replace" oor:type="oor:string-list">
<value>org.openoffice.lingu.basic.Thesaurus</value>
</prop>
</node>
<node oor:name="SpellCheckerList">
<prop oor:name="de-DE" oor:op="replace" oor:type="oor:string-list">
<value>org.openoffice.lingu.MySpellSpellChecker</value>
</prop>
<prop oor:name="de-AT" oor:op="replace" oor:type="oor:string-list">
<value>org.openoffice.lingu.MySpellSpellChecker</value>
</prop>
<prop oor:name="en-US" oor:op="replace" oor:type="oor:string-list">
<value>org.openoffice.lingu.MySpellSpellChecker</value>
</prop>
<prop oor:name="nl-BE" oor:op="replace" oor:type="oor:string-list">
<value>org.openoffice.lingu.MySpellSpellChecker</value>
</prop>
<prop oor:name="nl-NL" oor:op="replace" oor:type="oor:string-list">
<value>org.openoffice.lingu.MySpellSpellChecker</value>
</prop>
</node>
<node oor:name="ThesaurusList">
<prop oor:name="de-DE" oor:op="replace" oor:type="oor:string-list">
<value>org.openoffice.lingu.basic.Thesaurus</value>
</prop>
<prop oor:name="en-US" oor:op="replace" oor:type="oor:string-list">
<value>org.openoffice.lingu.basic.Thesaurus</value>
</prop>
</node>
</node>
<node oor:name="General">
<prop oor:name="DefaultLocale" oor:type="xs:string">
<value>'"${USELOCALE}"'</value>
</prop>
<node oor:name="DictionaryList">
<prop oor:name="ActiveDictionaries" oor:type="oor:string-list">
<value>soffice.dic sun.dic IgnoreAllList</value>
</prop>
</node>
</node>
</oor:component-data>' > "$LOCALOFFICE/user/registry/data/org/openoffice/Office/Linguistic.xcu"

# Language
echo '<?xml version="1.0" encoding="UTF-8"?>
<oor:component-data xmlns:oor="http://openoffice.org/2001/registry" xmlns:xs="http://www.w3.org/2001/XMLSchema" oor:name="Setup" oor:package="org.openoffice">
<node oor:name="Office">
<prop oor:name="ooSetupInstallPath" oor:type="xs:string">
<value>'"$LOCALOFFICE"'/user</value>
</prop>
</node>
<node oor:name="Configuration">
<prop oor:name="TransferUserSettingsOnce" oor:type="xs:boolean">
<value>false</value>
</prop>
</node>
<node oor:name="L10N">
<prop oor:name="ooLocale" oor:type="xs:string">
<value>'"$USELOCALE"'</value>
</prop>
</node>
</oor:component-data>' > "$LOCALOFFICE/user/registry/data/org/openoffice/Setup.xcu"

# End autoinstall
fi

# Font bug workaround for OpenOffice 1.0
[ -z "$LOCALOFFICE" ] && LOCALOFFICE=$(awk '/^OpenOffice\.org/{dir=substr($0,match($0,"file://")+7)}END{gsub(/[\n\r]/,"",dir);print dir}' $HOME/.sversionrc 2>/dev/null)
[ -e "$LOCALOFFICE/user/psprint/pspfontcache" ] && rm -f "$LOCALOFFICE/user/psprint/pspfontcache"

# Start openoffice
echo "Starting OpenOffice.org." >&2
( exec $CHECKMEM "$PROGRAM_PATH"/soffice "$@" & )
sleep 5
i=0; while [ "$i" -lt 120 ]; do sleep 2; xwininfo -root -tree | grep -q 'OpenOffice.org '; [ "$?" = "0" ] && break; i=`expr $i + 2`; done
kill $xpid 2>/dev/null
exit 0

Craig2
05-13-2004, 05:16 AM
I believe that's all of the rest of it. It starts about ten lines above where you were interested, so the very beginning is missing, but can be seen at my earlier post.

user unknown
05-13-2004, 12:11 PM
It looks as if there are preparations for english.
You could consider changing the first lines to avoid installing a german version again, and exit the script, like this:


case "$USELANGUAGE" in
de|ch|at)
#USELOCALE=de-DE
exit
;;
nl)
#USELOCALE=nl-NL
exit
;;

Markus
05-13-2004, 06:36 PM
Do you actually have the english language package for openoffice?

sh-2.05b$ COLUMNS=160 dpkg -l|grep -w en
ii myspell-en-us 20030813-3 English (US) dictionary for myspell
ii openoffice.org-help-en 1.1+20030814-3 OpenOffice.org office suite help (English)
ii openoffice.org-hyphenation-en-us 20030813-3 English (US) hyphenation pattern for OpenOffice.org
ii openoffice.org-l10n-en 1.1.1-2 English (US) language package for openoffice.org
ii trans-de-en 1.3-3 A German-English translation dictionary

sh-2.05b$ locate openoffice.org |grep -w en
Should also give some output.