Re: [gentoo-user] KDE and OpenOffice keyboard problems [solved]

2006-05-11 Thread Dave Jones
Bo Andresen wrote on 10/05/06 12:55:
For some strange reason, on my system OpenOffice seems to need the
locale set to utf8 to work properly with international keyboard layouts.
Without it, the ' and  keys are dead,  working only with AltGr pressed.

I don't understand why, but since I changed my locale to en_US.utf8, the
quote keys and Open Office work perfectly.

 Does this not work for you (# means run as root, $ means run as user)?
 # localedef -i en_GB -f ISO-8859-15 en_GB.ISO-8859-15
 $ LC_ALL=en_GB.ISO-8859-15 oowriter2

The LC_ALL command above did not work, giving the following error messages:

I18N: X Window System doesn't support locale en_GB.ISO-8859-15
Qt: Locales not supported on X server

Checked out my defined locales with locale -a

C
en_GB
en_GB.iso885915
en_GB.utf8
en_US
en_US.iso885915
en_US.utf8
POSIX

LC_ALL=en_GB.iso885915 oowriter2works fine.

In fact, all the above locales except for C and POSIX work fine in
OpenOffice. It seems that OOo does not depend on a utf8 locale, but does
needs a local other the C or POSIX.

Cheers, Dave
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] KDE and OpenOffice keyboard problems [solved]

2006-05-11 Thread Bo Andresen
On Thursday 11 May 2006 12:53, Dave Jones wrote:
  $ LC_ALL=en_GB.ISO-8859-15 oowriter2

 The LC_ALL command above did not work, giving the following error messages:

 I18N: X Window System doesn't support locale en_GB.ISO-8859-15
 Qt: Locales not supported on X server

 Checked out my defined locales with locale -a
[SNIP]
 LC_ALL=en_GB.iso885915 oowriter2works fine.

 In fact, all the above locales except for C and POSIX work fine in
 OpenOffice. It seems that OOo does not depend on a utf8 locale, but does
 needs a local other the C or POSIX.

Which is what I stated on the 4th of May. :) But en_GB.ISO-8859-15 works for 
me too even though locale -a report en_GB.iso885915 on my computer too. I 
guess that depends on the version of glibc.. Anyway nice to know it works for 
you now. :)

-- 
Bo Andresen


pgp5oUi7LKkyn.pgp
Description: PGP signature


Re: [gentoo-user] KDE and OpenOffice keyboard problems [solved]

2006-05-11 Thread Dave Jones
Bo Andresen wrote on 11/05/06 13:17:
LC_ALL=en_GB.iso885915 oowriter2works fine.

In fact, all the above locales except for C and POSIX work fine in
OpenOffice. It seems that OOo does not depend on a utf8 locale, but does
needs a local other the C or POSIX.

 Which is what I stated on the 4th of May. :) But en_GB.ISO-8859-15 works for 
 me too even though locale -a report en_GB.iso885915 on my computer too. I 
 guess that depends on the version of glibc.. Anyway nice to know it works for 
 you now. :)

I'm using glibc-2.3.6-r3 (stable branch).  Your statement on May 4 was
correct, and believe me, I'm very glad that the problem is solved here!

Pawel has not reported back from my last suggestion of trying to use the
us_intl keyboard layout.  It would be nice if that solved his problems
with his Polish locale/keyboard too.

I still find it strange that OOo is the only application I have which
needs a locale other than C or POSIX defined.

Cheers, Dave
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] KDE and OpenOffice keyboard problems [solved]

2006-05-10 Thread Bo Andresen
On Thursday 04 May 2006 15:29, Dave Jones wrote:
 I didn't get these errors when I ran the oowriter2 command above, so I
 guess my localdef for the en_GB.utf8 must have been OK.

 Case closed, an irritating problem fixed.

From another thread:

On Tuesday 09 May 2006 20:31, Dave Jones wrote:
 For some strange reason, on my system OpenOffice seems to need the
 locale set to utf8 to work properly with international keyboard layouts.
 Without it, the ' and  keys are dead,  working only with AltGr pressed.

 I don't understand why, but since I changed my locale to en_US.utf8, the
 quote keys and Open Office work perfectly.

Does this not work for you (# means run as root, $ means run as user)?

# localedef -i en_GB -f ISO-8859-15 en_GB.ISO-8859-15

$ LC_ALL=en_GB.ISO-8859-15 oowriter2

-- 
Bo Andresen


pgp7jTMR4TFw9.pgp
Description: PGP signature


Re: [gentoo-user] KDE and OpenOffice keyboard problems [solved]

2006-05-10 Thread Dave Jones
Bo Andresen wrote on 10/05/06 12:55:
 On Tuesday 09 May 2006 20:31, Dave Jones wrote:

For some strange reason, on my system OpenOffice seems to need the
locale set to utf8 to work properly with international keyboard layouts.
Without it, the ' and  keys are dead,  working only with AltGr pressed.

I don't understand why, but since I changed my locale to en_US.utf8, the
quote keys and Open Office work perfectly.

 Does this not work for you (# means run as root, $ means run as user)?

 # localedef -i en_GB -f ISO-8859-15 en_GB.ISO-8859-15
 $ LC_ALL=en_GB.ISO-8859-15 oowriter2

No, it doesn't work, I get these error messages when I try to start
oowriter2:

I18N: X Window System doesn't support locale en_GB.ISO-8859-15
Qt: Locales not supported on X server

The accented keys don't work either with this setup.

Cheers, Dave
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] KDE and OpenOffice keyboard problems [solved]

2006-05-04 Thread Dave Jones
Bo Andresen wrote on 05/04/06 00:48:

 It turns out I was wrong about this. If I type

 # LC_ALL=POSIX oowriter2

 they don't work for me either. Same goes for LC_ALL=C. All other locales on 
 your list from locale -a they do work with. (Except en_GB.utf8 which results 
 in a lot of errors on my system. That's why I use en_US.utf8. If you do wish 
 to use UTF-8 you should follow the guide provided by Gentoo). So try changing 
 your locale to something other than POSIX or C i.e. export LC_ALL=whatever. 
 And start OOo from the prompt.

 To change your locale permanently you should change /etc/env.d/02locale and 
 run env-update. You only need to set LC_ALL it will all other LC_ variables.

Bo, thank you *very* much, starting oowriter2 as you suggested using
LC_All=en_US.utf8 oowriter2 worked, the us_intl keyboard now works as it
should.

I have no /etc/env.d/02locale file; did you create that file yourself?

Cheers, Dave
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] KDE and OpenOffice keyboard problems [solved]

2006-05-04 Thread Bo Andresen
On Thursday 04 May 2006 11:17, Dave Jones wrote:
 Bo, thank you *very* much, starting oowriter2 as you suggested using
 LC_All=en_US.utf8 oowriter2 worked, the us_intl keyboard now works as it
 should.

Glad to hear that. :)

 I have no /etc/env.d/02locale file; did you create that file yourself?

Yes, just create a file with the contents:

LC_ALL=whatever

Look at [1] and [2] for more information on locales on Gentoo.

[1] http://www.gentoo.org/doc/en/guide-localization.xml#doc_chap3
[2] http://www.gentoo.org/doc/en/utf-8.xml

-- 
Bo Andresen


pgphsoHobO0Et.pgp
Description: PGP signature


Re: [gentoo-user] KDE and OpenOffice keyboard problems [solved]

2006-05-04 Thread Dave Jones
Bo Andresen wrote on 04/05/06 11:32:
 On Thursday 04 May 2006 11:17, Dave Jones wrote:

Bo, thank you *very* much, starting oowriter2 as you suggested using
LC_All=en_US.utf8 oowriter2 worked, the us_intl keyboard now works as it
should.

 Glad to hear that. :)

What's more, it seems to work fine with LC_ALL=en_GB.utf8 too.

As a matter of curiosity, what errors did you get when you tried
en_GB.utf8 on your system?

I have no /etc/env.d/02locale file; did you create that file yourself?

 Yes, just create a file with the contents:

 LC_ALL=whatever

OK, done that, it's working perfectly now.

 Look at [1] and [2] for more information on locales on Gentoo.

 [1] http://www.gentoo.org/doc/en/guide-localization.xml#doc_chap3
 [2] http://www.gentoo.org/doc/en/utf-8.xml

Will do, to check out any extra information available there.

Again, thank you both very much.  Your and Jerônimo's help and advice
solved an obscure problem which has annoyed me for months.

The Gentoo user community has yet again proven to be a great place to
finding helpful and knowledgeable people, adding to the many strengths
of the distro.

Glad to be part of it!

Cheers, Dave
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] KDE and OpenOffice keyboard problems [solved]

2006-05-04 Thread Bo Andresen
On Thursday 04 May 2006 12:08, Dave Jones wrote:
 As a matter of curiosity, what errors did you get when you tried
 en_GB.utf8 on your system?

$ LC_ALL=en_GB.utf8 oowriter2
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = en_GB.utf8,
LANG = (unset)
are supported and installed on your system.
perl: warning: Falling back to the standard locale (C).
I18N: Operating system doesn't support locale 

IIRC back when I followed the UTF-8 guide localedef complained that some data 
for creating the en_GB.UTF-8 locale was missing. It seems that the issue has 
been resolved since then. The following command fixed the problem so 
en_GB.utf8 is working for me too now:

# localedef -i en_GB -f UTF-8 en_GB.UTF-8

-- 
Bo Andresen


pgp3bNdR1D0qE.pgp
Description: PGP signature


Re: [gentoo-user] KDE and OpenOffice keyboard problems [solved]

2006-05-04 Thread Dave Jones
Bo Andresen wrote on 04/05/06 12:44:
 On Thursday 04 May 2006 12:08, Dave Jones wrote:

As a matter of curiosity, what errors did you get when you tried
en_GB.utf8 on your system?

 $ LC_ALL=en_GB.utf8 oowriter2
 perl: warning: Setting locale failed.
 perl: warning: Please check that your locale settings:
 LANGUAGE = (unset),
 LC_ALL = en_GB.utf8,
 LANG = (unset)
 are supported and installed on your system.
 perl: warning: Falling back to the standard locale (C).
 I18N: Operating system doesn't support locale 

 IIRC back when I followed the UTF-8 guide localedef complained that some data 
 for creating the en_GB.UTF-8 locale was missing. It seems that the issue has 
 been resolved since then. The following command fixed the problem so 
 en_GB.utf8 is working for me too now:

 # localedef -i en_GB -f UTF-8 en_GB.UTF-8

I didn't get these errors when I ran the oowriter2 command above, so I
guess my localdef for the en_GB.utf8 must have been OK.

Case closed, an irritating problem fixed.

Cheers, Dave
-- 
gentoo-user@gentoo.org mailing list