On Thu, Sep 07, 2006 at 11:07:02AM +0200, Jan Willem Stumpel wrote:
> Package: xkb-data
> Version: 0.8-12
> 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.
But we cannot be sure that they will enter testing together, so adding a
transition plan is desired. Here is mine:
1. Rewrite /usr/share/X11/locale/el_GR.UTF-8/Compose to include
/usr/share/X11/locale/en_US.UTF-8/Compose (as in pt_BR.UTF-8) and
only add Greek specific compose sequences.
2. Add compose sequences with U0313 and U0314 to en_US.UTF-8/Compose.
Note that this file already contains such sequences, so maybe there
is nothing to do here.
3. Push these changes upstream.
4. When en_US.UTF-8/Compose and el_GR.UTF-8/Compose are fixed in
testing, modify xkb/symbols/gr as requested, and close #386385.
5. Drop el_GR.UTF-8/Compose after etch if this file becomes useless.
If this roadmap makes sense to you, can you please file bug reports with
patches against libx11-data for steps 1 and 2?
This is much easier to perform by people reading Greek ;)
Denis
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
