Package: libx11-data
Version: 2:1.0.0-8
Severity: normal
This is a 'simultaneous bug' in xkb-data and libx11-data.
In /usr/share/X11/xkb/symbols/gr, the keys generating the Classical Greek
'breathing' signs are defined as follows
key <AC10> { [ dead_acute, dead_horn ] };
key <AC11> { [ dead_grave, dead_ogonek ] };
The breathing signs are the "shifted" symbols (dead_horn and dead_ogonek).
This means that these keys do not work in an international UTF-8 locale,
because the international Compose file
(/usr/share/X11/locale/en_US.UTF-8/Compose), which has definitions for the
full set of Ancient Greek accent combinations, expects the breathing signs
to be U0313 and U0314 respectively.
The dead_horn and dead_ogonek are only recognized by the Greek UTF-8 Compose
file, /usr/share/X11/locale/el_GR.UTF-8/Compose.
The solution is to change dead_horn to U0313 and dead_ogonek to U0314 both
in /usr/share/X11/xkb/symbols/gr and in
/usr/share/X11/locale/el_GR.UTF-8/Compose. It is important to do this
simultaneously.
That way it will become possible to enter Classical Greek correctly both in
"international" and Greek UTF-8 locales. I expect, in fact, that the reason
for having a separate Greek UTF-8 compose file will then largely disappear
(although with the proposed changes in place, there will no longer be any
harm in keeping it).
Because there must be simultaneous changes in the xkb gr file and the Greek
Compose file, a careful transition plan is needed. Please see bug 386385,
and the discussion there, which includes a proposal for patching the Gree
Compose file.
Regards, Jan
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Versions of packages libx11-data depends on:
ii x11-common 1:7.0.23 X Window System (X.Org) infrastruc
libx11-data recommends no packages.
-- debconf-show failed
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
