Issue 22694 - Compose key does not work in Redhat9
Summary: Compose key does not work in Redhat9
Status: CLOSED DUPLICATE of issue 32772
Alias: None
Product: Internationalization
Classification: Code
Component: ui (show other issues)
Version: OOo 1.1
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: ulf.stroehler
QA Contact: issues@l10n
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2003-11-21 03:38 UTC by pbwest
Modified: 2004-12-13 11:05 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description pbwest 2003-11-21 03:38:37 UTC
Compose key functionality is not available under RH9, in a KDE desktop
environment.  The locale is en_AU.UTF-8.  Compose works in gnome-terminal, gedit
and mozilla (with utf-8 as the character coding.)  It does not work for OO 1.1,
or the KDE app Konsole or Java apps.
Comment 1 mci 2003-11-21 14:37:16 UTC
reassigned to mci
Comment 2 mci 2003-11-21 14:59:08 UTC
Hi pbwest,

thanks for using and supporting openOffice...

I think redhat-config-language will be your friend :)
With this program you set your "global" settings in /etc/sysconfig/i18n...

We tried this on a Redhat Linux 9.0 using OOo 1.10 and then it worked...

If I'm right the gnome-applications and some other do a "fallback" to
an iso8859-1 locale since in the systemwide config file for language
settings (/usr/X11R6/lib/locale/locale.alias) there are no entries for
en_AU.utf8...
Comment 3 mci 2003-11-21 15:07:43 UTC
This seems to be same as issue 16318...

You may have a look to this: 
http://wauug.erols.com/~balsa/linux/deadkeys/


closing...
Comment 4 pbwest 2003-11-21 15:34:56 UTC
Here's the current content of my /etc/sysconfig/i18n

LANG="en_AU.UTF-8"
SUPPORTED="en_AU.UTF-8:en_AU:en:en_US.UTF-8:en_US:en"
SYSFONT="latarcyrheb-sun16"

What's the deal here?  To what am I suppose to set my locale?  What
exactly does X emit when I use the Compose key?  A UTF-8 sequence?  An
iso8859-1 (or -15) 8-bit character?  What goes on?  How and where do I
find out?

What does OO expect. given the above locale info?  If I set my locale
to en_US.UTF-8, e.g., what will X send to OO, and what will OO be
expecting?

Are UTF-8 locales supported at all?
Comment 5 pbwest 2003-11-27 15:12:05 UTC
Re-opening pending some feedback on my last comments.
Comment 6 mci 2004-01-07 10:12:31 UTC
added mci to cc

reassigned to us

Hi us,
this is the Issue we talked about...
Comment 7 ulf.stroehler 2004-01-07 10:58:42 UTC
en_AU.UTF-8 works flawless for me with OOo 1.1 on RH9 no matter which desktop
system is chosen.
If you'd like to know what xevent is triggered when hitting specific keys try xev.

=>WFM.
Comment 8 ulf.stroehler 2004-01-07 11:04:48 UTC
Building compose key sequences was ment (of course) with the above statement
regarding flawless working of en_AU.UTF-8.
Comment 9 ulf.stroehler 2004-01-07 16:50:39 UTC
Additional hint:
man XmbLookupString
Comment 10 pbwest 2004-01-08 04:52:13 UTC
I'm pleased it WORKSFORYOOU.  Unfortunately, it DOESN'TWORKFORME.  xev, as
expected,shows Multi-Key, "e", "'" (or whatever sequence I am using.  This
composed key appears in gnome-terminal, but does not appear in OO.  I get
nothing.  However, I get the same negative result in an xterm.  It appears that
only Gnome apps are happy with Compose.
Comment 11 ulf.stroehler 2004-01-08 14:38:07 UTC
@submitter: if it doesn't work for you in xterm either (for me it does); what is
the outcome, if you enter the command "locale" in xterm?
Comment 12 pbwest 2004-01-08 16:28:43 UTC
en_AU.UTF-8

Thanks for your attention to this.  I have also asked the question on the
XFree86 list.
Comment 13 ulf.stroehler 2004-07-20 16:01:07 UTC
Re-verified on fedora core 2.
Additionally Xkeyboard events are handled by gtk in 680s developer versions, if
being in an GNOME environment. Thus the same compose keys/sequences working in a
gnome-terminal should work the same way in OO.o 680s.
Precondition: enabled dead keys in XF86Config resp. xorg.conf.
Comment 14 pbwest 2004-10-03 15:12:34 UTC
This issue has resurfaced for me.  I am now running Fedora Core 2 with a Gnome
desktop.  When I installed FC2, I also installed the FC2-supplied 1.1.1.  My
compose key worked. Alleliua!  When I downloaded and installed 1.1.2 from
OO.org, my Compose functionality disappeared again.  Same story.  Works in Gnome
apps and mozilla.  Doesn't work in KDE apps, xterm, OpenOffice or Netbeans.

Note that I don't have deadkeys enabled.  I specifically do not want deadkeys,
because the vast majority of text I create is English, and deadkeys are a pain
for English input.  Compose works a treat for occasional non-ascii characters.

What do Redhat do in their build which would make the difference?

Output from 'locale'
LANG=en_AU.UTF-8
LC_CTYPE="en_AU.UTF-8"
LC_NUMERIC="en_AU.UTF-8"
LC_TIME="en_AU.UTF-8"
LC_COLLATE="en_AU.UTF-8"
LC_MONETARY="en_AU.UTF-8"
LC_MESSAGES="en_AU.UTF-8"
LC_PAPER="en_AU.UTF-8"
LC_NAME="en_AU.UTF-8"
LC_ADDRESS="en_AU.UTF-8"
LC_TELEPHONE="en_AU.UTF-8"
LC_MEASUREMENT="en_AU.UTF-8"
LC_IDENTIFICATION="en_AU.UTF-8"
LC_ALL=
Comment 15 pbwest 2004-10-03 22:29:41 UTC
Compose also works in Eclipse.  Note - doesn't work in NetBeans.  Is this a
GTK-related issue?
Comment 16 thackert 2004-12-12 11:26:17 UTC
I have seen that the last entry was in October and that it is OOo-1.1related. Have you tried this with a 
newer version of OOo (1.1.x or 1.9.xx)? Does this problem also occur there? Or could this issue be 
closed?
Comment 17 pbwest 2004-12-12 12:10:18 UTC
Still a problem.  In fact, it's worse.  It used to work in one of the Redhat
distributed version, but not in openoffice.org-1.1.2-10.fc2 on Fedora C3.

The compose key works in here (firefox); e.g. é, ö, but not in the above OO, or
in the 1.1.3 that I downloaded directly some time back.  I haven't tried
1.1.4RC1 or 1.9 (which I presume is preparation for 2.0).
Comment 18 ulf.stroehler 2004-12-13 11:05:15 UTC
Pls. try the latest snapshot from:
http://download.openoffice.org/680/index.html

Regarding the last comments in this issue, it becomes kind of a dupe to issue 32772.
Refer to issue 32772 for a workaround.

*** This issue has been marked as a duplicate of 32772 ***
Comment 19 ulf.stroehler 2004-12-13 11:05:57 UTC
Closing dupe.