New composers for local languages in Togo
ran234 at gmail.com
Thu Feb 4 12:37:52 UTC 2016
On Tue, Jan 19, 2016 at 01:16:40AM +0100, Mats Blakstad wrote:
> I've opened this ticket:
> I need some feedback to be able to upload a final verion!
> How should the composer be formatted. Now each composer is added like this:
> *<dead_acute> <dead_tilde> <U0190> : "Ɛ̃́" LATIN CAPITAL
> LETTER EPSILON WITH TILDE AND ACUTE*
> But it looks like the other composer keys have a hash tag and the unicode
> after the quotation mark, like this:
> *<dead_acute> <dead_tilde> <U0190> : "Ɛ̃́" U+0190 # LATIN
> CAPITAL LETTER EPSILON WITH TILDE AND ACUTE*
> However, I need several unicodes to represent the symbols, like:
The format of Compose is
<sequence>: "<string>" <keysym>
<string> is arbitrary, but <keysym> can only be a single keysym. The
unicode character you quote is using combining characters, which are
not supported in the Compose format/XKB implemented in libX11,
unfortunately. So, you cannot specify something like
"U+0190U+0303U+0301" in the <keysym> part, only a single keysym/unicode
Your options are:
1. Use a precomposed character instead of the combining characters.
This doesn't always exist, I didn't check for the above. If one
exists, this is the best option.
2. Omit the keysym part. Some programs only use the string part, so this
might work well for you, but programs which want the keysym result
won't have it.
> How should I add this? Can I do like this:
> *<dead_acute> <dead_tilde> <U0190> : "Ɛ̃́" U+0190U+0303U+0301
> # LATIN CAPITAL LETTER EPSILON WITH TILDE AND ACUTE*
> Thanks in advance.
> xorg-devel at lists.x.org: X.Org development
> Archives: http://lists.x.org/archives/xorg-devel
> Info: http://lists.x.org/mailman/listinfo/xorg-devel
More information about the xorg-devel