Compose key on staroffice 6.0
Alan
The problem is that the compose key doesn't work as expected.
If I want to type a ó I press <compose> then apostrophe and then o, but I
get always a apostrophe before the ó.
The compose key is working on other programs that use gtk1, gtk2 or qt2.
I am using KDE and Icewm as my window managers, my LANG is set to C, but I
also tried with different LANGs.
This is the output of running xev and then pressing compose, apostrophe and
"a":
KeyPress event, serial 25, synthetic NO, window 0x5c00001,
root 0x25, subw 0x0, time 3696188893, (263,-159), root:(266,279),
state 0x0, keycode 108 (keysym 0xff20, Multi_key), same_screen YES,
XLookupString gives 0 characters: ""
KeyRelease event, serial 27, synthetic NO, window 0x5c00001,
root 0x25, subw 0x0, time 3696188973, (263,-159), root:(266,279),
state 0x0, keycode 108 (keysym 0xff20, Multi_key), same_screen YES,
XLookupString gives 0 characters: ""
KeyPress event, serial 27, synthetic NO, window 0x5c00001,
root 0x25, subw 0x0, time 3696194901, (263,-159), root:(266,279),
state 0x0, keycode 59 (keysym 0x27, apostrophe), same_screen YES,
XLookupString gives 0 characters: ""
KeyRelease event, serial 27, synthetic NO, window 0x5c00001,
root 0x25, subw 0x0, time 3696194997, (263,-159), root:(266,279),
state 0x0, keycode 59 (keysym 0x27, apostrophe), same_screen YES,
XLookupString gives 0 characters: ""
KeyPress event, serial 27, synthetic NO, window 0x5c00001,
root 0x25, subw 0x0, time 3696201309, (263,-159), root:(266,279),
state 0x0, keycode 11 (keysym 0xe1, aacute), same_screen YES,
XLookupString gives 1 characters: "á"
KeyRelease event, serial 27, synthetic NO, window 0x5c00001,
root 0x25, subw 0x0, time 3696201405, (263,-159), root:(266,279),
state 0x0, keycode 11 (keysym 0xe1, aacute), same_screen YES,
XLookupString gives 1 characters: "á"
Can anybody help me?
Regards
Alan
Nils Homp - Sun StarNews Support
StarOffice uses the function XmbLookupString (keyboard event handling
function) and IIIMP (IntranetInternetInputMethodProtocol) to allow
multilingual text input under Unix. The encoding for the XmbLookupString
is always based upon the input method used. In this particular case, the
IIIMP method consistently uses UTF-8.
This is why StarOffice reacts in an ISO8859 locale the same as it does
in an UTF-8 locale - with all features as well as problems. The
"SunXK_FA_Grave" key, that does not function in an UTF-8 locale, is an
example.
All text input (XmbLookupString) is controlled by the locale. This means
that the XmbLookupString is not active if you are not using locales or
are using the locale "C", and characters higher than 256 cannot be
addressed. The XLookupString is used instead; however, this works in the
ISO8859-1 indication range also known as Latin-1.
A well-known limitation with the Xlib (XLookupString is an Xlib based
function) is that it cannot use the [Compose] key.
Further information on how to use the Compose key can be found at the
following web site:
http://docs.sun.com/db/doc/806-4743/6jdq6q25k?q=compose+key+sequences&a=view
I hope this will be of some help.
Regards,
Nils Homp
Sun StarNews Support
--
All responses posted to this newsgroup are provided without guarantees
as to the suitability of their use. Although we believe the solutions or
explanations given to be accurate and correct, we cannot guarantee the
accuracy of the information contained.
Please do not reply directly to this e-mail address if you wish to
continue further dicussion of this matter, as you will only receive an
automatic response from our system. Instead, please reply to the message
itself so further assistance can be provided via the newsgroup.
Alternatively, you are welcome to have a look at our website for further
information regarding our support services, which is available at
http://www.sun.com/star/support