Issue 12636 - Keyboard layout shouldn't depend on LC_*
Summary: Keyboard layout shouldn't depend on LC_*
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Internationalization
Classification: Code
Component: ui (show other issues)
Version: 644
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: jack.warchold
QA Contact: issues@l10n
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-03-25 10:17 UTC by Unknown
Modified: 2010-10-23 15:34 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2003-03-25 10:17:38 UTC 
It is widely reported to people complaining that they're having keyboard
problems (like dead keys not working), that they are probably running OOo in the
wrong locale.
And this is true: for example, I have a Swiss French keyboard, and dead keys
only work if I set LC_ALL to fr_CH.

The problem is: this is dead wrong from a design point of view. The LC_*
environment variables are meant in the POSIX standard to define the _output_
language, they have _nothing_ to do with keyboard layout.

OOo should use the keyboard layout defined by the X server and stick to it.
Imagine that I have a PC in front of me with a Polish keyboard, but I'm speaking
French. What has the keyboard layout to do with the displayed language ? 
Nothing ! 

In the current state, OOo is the _only_ application in the world using the LC_*
variables to specify the keyboard layout, and that's definitely not a feature.
Comment 1 Unknown 2003-03-25 11:05:44 UTC 
IMHO, X-Windows based implementations should use XLookupString or
something similar to translate keypresses into characters, taking into
account the current X server keymap.
Comment 2 Unknown 2003-04-10 15:39:42 UTC 
Actually they should use X's default input mechanism to convert keys
into characters, whatever this mechanism is (input methods,...)
Comment 3 jack.warchold 2003-12-01 16:07:11 UTC 
reassigend to jw
Comment 4 jack.warchold 2003-12-01 16:08:00 UTC 
closed due the long time of inactivity

please feel free to reopen this issue if this error still occurs on 
your system with the latest office release
Comment 5 jack.warchold 2003-12-01 16:08:21 UTC 
wfm -> closed
Comment 6 panricarfe 2010-10-23 15:34:10 UTC 
Created attachment 72549