DL->CP: Would you please takeover?

what happens if you set LANG to en_GB, too ? what about LC_ALL ? how
do you enter the chars (deadkey / compose key / keyboard support ...)
? do you use the xkeyboard extension ? 

>what happens if you set LANG to en_GB, too ?
> what about LC_ALL ?

If I set LANG and LC_ALL to en_GB.utf8, the problem persists.

gee@swordfish:~% locale
LANG=en_GB.utf8
LC_CTYPE="en_GB.utf8"
LC_NUMERIC="en_GB.utf8"
LC_TIME="en_GB.utf8"
LC_COLLATE="en_GB.utf8"
LC_MONETARY="en_GB.utf8"
LC_MESSAGES="en_GB.utf8"
LC_PAPER="en_GB.utf8"
LC_NAME="en_GB.utf8"
LC_ADDRESS="en_GB.utf8"
LC_TELEPHONE="en_GB.utf8"
LC_MEASUREMENT="en_GB.utf8"
LC_IDENTIFICATION="en_GB.utf8"
LC_ALL=en_GB.utf8
gee@swordfish:~% openoffice
I18N: X Window System doesn't support locale "en_GB.utf8"

Now I have noticed, that I can enter 2 characters that are not in
the latin-1 set, these are: o and u with double long accent (acute I think)
The rest do not work.

If I set everything to en_GB, I can type all the characters, and also
when starting openoffice, I do not get the X Window System doesn't support
locale message.

> how do you enter the chars (deadkey / compose key / keyboard
> support ...)?
> do you use the xkeyboard extension ?

I use KDE, and I think KDE uses Xkeys. I am running a kde app that let's
me choose between some keyboard layouts, like US, FR, HU

It is possible that my X setup misses something, but I have these locales
installed:
gee@swordfish:~% locale -a
C
POSIX
en_GB
en_GB.utf8
en_US
hu_HU

Other programs (like Xemacs) are complaining about the lack of en_GB.utf8
support in xlib too, but the only place where this causes a problem for me
is OOo.

In version 1.0 OpenOffice did not start at all, it crashed and dumped core.
Now it starts, only the special characters are not working.

Regards

sorry, I will not handle this one soon. It is clearly a case of
misconfigured X Window system (X Window system does not support the
locales that your Operating System does) and OOo falls back the
portable "C" or "POSIX" locale where you are bound to 7 bit ASCII
characters. 

To get along for now, please add the lines
   LC_ALL=en_GB
   export LC_ALL
the the head of your "soffice" shell script that you find in the
program subdirectory of your OpenOffice.org installation

Um, I have the same problem (well, en_AU.utf8) here. All of my other
applications (gnome-terminal, gedit, ...) work properly in that locale.

I can't really see how it's an X problem if other apps are working OK.

Your other X application don't run well in that locale since 'X Window
System doesn't support locale "en_GB.utf8"'. They definitively can't
run well in that locale. They run well in any locale they have
silently chosen as a replacement. 

You wrote:
It is clearly a case of misconfigured X Window system (X Window system does not support the locales that your Operating System 
does) and OOo falls back the portable "C" or "POSIX" locale where you are bound to 7 bit ASCII characters. 

My problem with this is that instead of "C" or "POSIX" OOo falls back to something bad.

If I set everything to "C" or "POSIX", all my accented characters work. I am not bound to 7 bit, I can write characters from 
latin-1 and latin-2.
If I set en_GB.utf8, and you do the fallback, I cannot write latin-1 characters, nut latin-2 (at least ? (o with double acute)) 
works.

according to the announcement on releases
(http://www.openoffice.org/servlets/ReadMsg?list=releases&msgNo=7503) this issue
will be re-targeted to OOo Later.

we will fall back to en_US if we encounter an invalid locale. See i8988 for summary

implementation subtask to i8988

send to qa ...

reassign to Ulf

set back to fixed

Verified in cws 'vcl29'.

Verified on MWS m77.