Bug 10824 - greece polytonic - catastrophe!!!
Summary: greece polytonic - catastrophe!!!
Status: RESOLVED FIXED
Alias: None
Product: xkeyboard-config
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: All All
: medium normal
Assignee: xkb
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 9306
Blocks:
  Show dependency treegraph
 
Reported: 2007-05-01 08:04 UTC by Oleksij Rempel
Modified: 2007-05-07 15:50 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Oleksij Rempel 2007-05-01 08:04:23 UTC
What is working !?
I don't know if it's specific distribution( ubuntu 7.04 ) issue or it is so.
There is a big problem with greec polytonic, which is breathing important for me.
Every word in old greece use combinations like:
""ἁ"   U1F01 # GREEK SMALL LETTER ALPHA WITH DASIA"
""ἂ"   U1F02 # GREEK SMALL LETTER ALPHA WITH PSILI AND VARIA"
""ἀ"   U1F00 # GREEK SMALL LETTER ALPHA WITH PSILI"
.......
How to write all this???

en_US.UTF-8/Compose:
<U10000313> <Greek_alpha>               : "ἀ"   U1F00  <- not working
<Multi_key> <parenright> <Greek_alpha>  : "ἀ"   U1F00  <- working

<U10000314> <Greek_alpha>               : "ἁ"   U1F01  <- not working
<Multi_key> <parenleft> <Greek_alpha>   : "ἁ"   U1F01  <- working

<dead_grave> <U10001F00>                : "ἂ"   U1F02  <- not working
<Multi_key> <grave> <U10001F00>         : "ἂ"   U1F02  <- working
<dead_grave> <U10000313> <Greek_alpha>  : "ἂ"   U1F02  <- not working
<dead_grave> <Multi_key> <parenright> <Greek_alpha> : "ἂ"  <- working
<Multi_key> <grave> <U10000313> <Greek_alpha> : "ἂ"  <- working
<Multi_key> <grave> <parenright> <Greek_alpha> : "ἂ"  <- working
<combining_grave> <U10001F00>       : "ἂ"   U1F02  <- not working
<combining_grave> <U10000313> <Greek_alpha> : "ἂ"   U1F02 <- not working
<combining_grave> <Multi_key> <parenright> <Greek_alpha>  : "ἂ"   U1F02  <- not working


from two combinations working only one
<Multi_key> <parenright> <Greek_alpha>, this one need to be used like two time on three words. With modern keylayout symbols/gr(polytonic) it is fore keys !!!
<Multi_key> <Shift><parenright> <Greek_alpha>.


There is no problem to correct some key in this layout and make it more useful but how about this <U10000313> <Greek_alpha> it is more shorter.

Any idea how to make this working ?
Comment 1 Denis Barbier 2007-05-01 13:15:59 UTC
Sergey, there is some discussion at http://bugs.debian.org/386385
but I forgot to push these changes here, sorry.  As described in
this bugreport, changes must be synchronized with Compose files.
Comment 2 Sergey V. Udaltsov 2007-05-01 13:50:52 UTC
Denis,

I am not really excited about putting explicit unicode. But it seems the guy has the point. So what do you think now about changing dead_horn and dead_ogonek to U0314 and U0313?
Comment 3 Denis Barbier 2007-05-01 14:33:36 UTC
The problem is that el_GR.UTF-8/Compose contains sequences with
dead_* symbols, so it will not work anymore for people setting
LANG=el_GR.UTF-8.
Comment 4 Sergey V. Udaltsov 2007-05-01 14:37:19 UTC
I understand. But then Greeks would file a bug against libx11-data - and fix Compose files, wouldn't them?
Comment 5 Denis Barbier 2007-05-01 14:47:20 UTC
I agree, but it is surely better to make changes at the
same time to minimize trouble.
Comment 6 Sergey V. Udaltsov 2007-05-01 15:19:57 UTC
Unfortunately I cannot commit to core xorg. Denis, can you?
Comment 7 Denis Barbier 2007-05-01 15:32:07 UTC
No, I have no commit access to X.Org.
Comment 8 Sergey V. Udaltsov 2007-05-02 01:12:13 UTC
I think someone should make first step. Let it be us.

Alexey, once I commit unicode keysyms, could you please open bug against libx11-data so they would change Compose files?
Comment 9 Oleksij Rempel 2007-05-02 03:08:58 UTC
ok. do i need to know any other details?

Thank you for your work :)
Comment 10 Sergey V. Udaltsov 2007-05-02 14:48:44 UTC
Lads, I've committed the change. Alexey, please file a bug regarding Compose files - and do not forget to provide the reference to this bug.
Comment 11 James Cloos 2007-05-05 12:03:02 UTC
Compose change commited to libX11 git.
Comment 12 Alexandros Diamantidis 2007-05-06 13:16:38 UTC
Please note that even though U0314 and U0313 seem more correct, they aren't really the keysyms that should be used for this function. According to appendix A (KEYSYM encoding) of the X Window System Protocol Reference (ftp://ftp.x.org/pub/X11R7.0/doc/PDF/proto.pdf):

# Dead keys, which place an accent on the next character entered, shall be
# encoded as Function KEYSYMs, and not as the Unicode KEYSYM corresponding
# to an equivalent combining character.

So, the correct solution is to create two new keysyms for the dead keys for psili and daseia. I've opened bug #9306 for this - although if everyone starts using U0314 and U0313 as dead keysyms, as it seems to be happening, would they be willing to change everything yet again in the future?
Comment 13 Sergey V. Udaltsov 2007-05-07 04:16:01 UTC
I totally agree. Using direct unicode is a bad practice used only when keysyms are not available. Once X gets correct keysyms for this case, we'll replace unicode.
Comment 14 Simos Xenitellis 2007-05-07 04:45:11 UTC
James, I cannot see the change to the compose files at    http://gitweb.freedesktop.org/?p=users/whot/libX11.git;a=history;f=nls/en_US.UTF-8/Compose.pre

Am I looking at the wrong place?
Comment 15 James Cloos 2007-05-07 15:50:25 UTC
(In reply to comment #14)
> James, I cannot see the change to the compose files at   
> http://gitweb.freedesktop.org/?p=users/whot/libX11.git;a=history;f=nls/en_US.UTF-8/Compose.pre
> 
> Am I looking at the wrong place?
> 

Yes.  Try s(users/whot/libX11)(xorg/lib/libX11) to get:

http://gitweb.freedesktop.org/?p=xorg/lib/libX11.git;a=history;f=nls/en_US.UTF-8/Compose.pre

The commit itself is:

http://gitweb.freedesktop.org/?p=xorg/lib/libX11.git;a=commit;h=c76d30253f1483ac8200ad5c032a818907e65030

Incidentally, perhaps I was too quick to close the other bug; there will need to be an actual release of libX11 before the next release of xkeyboard-config, yes?


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.