Summary: | missing Compose sequences | ||
---|---|---|---|
Product: | xorg | Reporter: | Joachim Breitner <mail> |
Component: | Lib/Xlib | Assignee: | Xorg Project Team <xorg-team> |
Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | normal | ||
Priority: | medium | CC: | simos.bugzilla |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Joachim Breitner
2007-03-24 05:14:41 UTC
> But these don't
> <Multi_key> acute c
> <Multi_key> cedilla c
> etc.
The first exists,
<Multi_key> <acute> <c> : "ć" U0107 # LATIN SMALL LETTER C WITH ACUTE
but the second does not.
So, should <Multi_key> <cedilla> entries be added duplicating the 36 instances of <Multi_key> <comma> tuples? (That covers adding cedilla to both cases of: cdeghklnrstćĕ ) <Multi_key> <cedilla> tuples akin to the existing <Multi_key> <comma> tuples added to en_US and pt_BR UTF-8 Compose.pre files for UCS characters with CEDILLAs in commit 254522d3c24e0590732fc03cdd61ff4564819d94. Hi, Thanks for fixing this. Just wondering: Why only for these two locales? Joachim > Just wondering: Why only for these two locales?
Most of the UTF-8 locales use the en_US.UTF-8 Compose.pre.
The other UTF-8 locales with distinct Compose.pre files lack any
‘WITH CEDILLA’ characters or — in el_GR’s case — lack UCS names
in the comment section of the lines and therefore were missed
when I grep(1)ed. . . .
And I completely forgot to consider the 8859 locales. :-/
Thanks for the reminder!
Commit 55248e5c84c3fd8c349a3bb4cb15a1ec86989d74 completes the updates: The last commit missed the el_GR UTF-8 Compose.pre as well as the various ISO 8859 locales which have compose sequences generating ‘WITH CEDILLA’ characters. (Interestingly, some of the 8859 locales already supported <Multi_key> <cedilla> for some CEDILLA characters, but not for Ç or ç.) |
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.