| Summary: | Additions to X11/locale/en_US.UTF-8 | ||
|---|---|---|---|
| Product: | xorg | Reporter: | Geoff Streeter <geoff> |
| Component: | Lib/Xlib (data) | Assignee: | Xorg Project Team <xorg-team> |
| Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> |
| Severity: | trivial | ||
| Priority: | low | ||
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | 2011BRB_Reviewed | ||
| i915 platform: | i915 features: | ||
| Attachments: | |||
That looks like a libX11 compose file, not an xkb-config file, so moving to the right place. Thank you. Where did it go to ? Since both projects are hosted on freedesktop.org, it was just moved to a different product & component in the same bugzilla instance. Please provide a *patch* rather than the updated file. Also, you should email your patch to the xorg-devel mailing list for review. Created attachment 55082 [details]
addition to be added to the bottom of Compose.pre
Compose.pre appears to be the same as Compose except that leading comment "#" are replaced by "XCOMM". So I have modified my additions accordingly.
Re: attachement #55082:
The circled letters and digits are alread in the utf8 Compose.pre using
»Multi_key ( letter )« suntax.
Sequences such as »Multi_key < =« and the like also are already there.
It is better to use the symbol names rather than Uxxxx names where
possible. Cf /usr/include/X11/keysym.h and /usr/include/X11/keysymdef.h
for the full list of defined symbols.
Non-APL-specific sequences should be sorted with the rest; this helps
self-document the various equivalent sequences.
Perhaps the APL-specific ones should, too. I understand that you
ordered them based on the keyboard, but most of the file is sorted
by the resulting string.
Ideally, git clone one of:
git://anongit.freedesktop.org/xorg/lib/libX11
http://anongit.freedesktop.org/git/xorg/lib/libX11.git
and use »git format-patch« to generate the patch.
Thanks. Complete support for entering APL is clearly beneficial.
Created attachment 55164 [details]
modified addition for en_US.UTF-8/Compose
I have restructured the additions to be in Unicode order.
I have coded all of the entries from "Mathematical Operators" that are used by any APLs that I am aware of. I have coded all of the APL FUNCTIONAL SYMBOLS in "Miscellaneous Technical" that are overstrikes.
I have left <_ in spite of <= already being there. This is because ancient APLers expect these. They are not critical though because ≤ is going to be on any APL keyboard. However ≠_ is more important because they may not have ≢.
There seems to be a problem with <macron>. I could not get ¯⊤ or ⊤¯ to work. Also the existing ¯A doesn't seem to work. I tried a Compose files with just the two lines and that did not work. I tried using <U00af> and that didn't work either.
I could not understand why _; didn't work. However, I did not go as far as testing it in an isolated file. I will try to find some time to do this.
I have left some non working lines in but commented them. This is so that others don't just think that I omitted them by mistake.
Sorry, but I didn't learn enough about "git format-patch" fast enough to use it.
This should be enough for extensive APL support. All of the issues are for characters that nobody is actually using for real APL. Of course that does not mean that nobody wants to type them anywhere.
Created attachment 55213 [details]
added comments re <underscore> <semicolon>
_; doesn't work because it clashes with _;O and _;o
Created attachment 55333 [details]
With the real changes to the comments
Sorry sent the previous one before I saved it to disk.
This was committed somewhere in May 2012. Closing. |
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.
Created attachment 54703 [details] A new version of en_US.UTF-8/Compose I have added lines to do composition to produce characters in the range U24b6 to U24CF (The circled capital alphabetics); the range U2460 to U2468 (the circled single digit numerics). I have added compositions for all of the APL characters generated by the keyboards in xkb/symbols/apl. I have the feeling that a lot of these compositions would be better in a "partsbin" directory and then the actual locale files built by including files from the parts bin. However, that is not what seems to be the culture for these files.