| Summary: | greece polytonic - catastrophe!!! | ||
|---|---|---|---|
| Product: | xkeyboard-config | Reporter: | Oleksij Rempel <linux> |
| Component: | General | Assignee: | xkb |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | CC: | simos.bugzilla |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Bug Depends on: | 9306 | ||
| Bug Blocks: | |||
|
Description
Oleksij Rempel
2007-05-01 08:04:23 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. 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? 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. I understand. But then Greeks would file a bug against libx11-data - and fix Compose files, wouldn't them? I agree, but it is surely better to make changes at the same time to minimize trouble. Unfortunately I cannot commit to core xorg. Denis, can you? No, I have no commit access to X.Org. 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? ok. do i need to know any other details? Thank you for your work :) 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. Compose change commited to libX11 git. 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? 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. 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? (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.