Patch for compose key sequences J with acute

[Pander]

On 2013-02-20 17:28, James Cloos wrote:
> One quick review note:
> 
> Per 10646 and unicode, that miniscule sequence should
> be <U+006A U+0301> "j́" and not <U+0237 U+0303> "ȷ́".

Do you mean (only fix in tyop in quote of my proposal):

<U+006A U+0301> "j́" and not <U+0237 U+0301> "ȷ́".

I just noticed that on bitmap fonts such as the command line, one still
sees the dot of the j or a j followed by a filled diamond shape.

> The i and j are defined to have soft dots; all combining sequence
> starting with either MUST ignore the dot on the base character.
> 
> Not all font/rendering engines tuples get this right, but they should,
> and searches et al probably expect j́.

So indeed there is some work on the rendering part. Attached is a new
patch with you improvement. Does anyone would like to have the reverse
order supported and/or dead keys supported for this?

> -JimC
> 

Regards,

Pander
-------------- next part --------------
A non-text attachment was scrubbed...
Name: libx11-compose-key-j-acute-0.2.patch
Type: text/x-patch
Size: 1469 bytes
Desc: not available
URL: <http://lists.x.org/archives/xorg-devel/attachments/20130221/679302fd/attachment-0001.bin>