Bug 73293 - kbd: some compose combinations missing
Summary: kbd: some compose combinations missing
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: kbd   
(Show other bugs)
Version: 1.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Eido Inoue
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2002-09-02 16:11 UTC by Moritz Barsnick
Modified: 2007-04-18 16:46 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-07-14 16:29:28 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Moritz Barsnick 2002-09-02 16:11:40 UTC
Description of Problem:

When using a keymap which includes "compose.latin1", some compose
combinations don't work, such as 'a"' (all vowels).

Version-Release number of selected component (if applicable):

How Reproducible:

Steps to Reproduce:
1. loadkeys de-latin-nodeadkeys.map
2. Type the selected compose key (Alt+AltGr), then 'a', then '"'

Actual Results:
Console shows 'a"'

Expected Results:
Console shows 'd' (a-Umlaut)

Additional Information:
In many X11 compose keymaps, the order of the composed characters
is irrelevant, i.e. 'a"' is equivilant to '"a' (and even more common to
use). kbd supportst he latter, but not the former. Compare
/usr/X11R6/lib/X11/locale/iso8859-1/Compose .

Comment 1 Eido Inoue 2003-01-06 02:51:29 UTC
so your bug is that compose only accepts one combination, and you want both
combinations to be accepted?

Comment 2 Moritz Barsnick 2003-01-13 11:13:18 UTC
Indeed, I expect the same behavior as under X11, as this is where this method
is derived from (as far as I'm aware), and many people are used to those key 

Perhaps an automatic conversion / adaptation from
usr/X11R6/lib/X11/locale/iso8859-1/Compose may be possible.


Comment 3 Eido Inoue 2003-07-14 16:29:28 UTC
non-ASCII input into the console won't be supported on UTF-8 based systems (RHL
8+) until the kernel supports it. See the release notes in the next beta for
more info. Of course, input through X will always be supported.

Note You need to log in before you can comment on or make changes to this bug.