[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bidi and shaping problems in describe-input-method

From: Eli Zaretskii
Subject: Re: bidi and shaping problems in describe-input-method
Date: Fri, 09 Mar 2012 18:15:18 +0200

> From: Kenichi Handa <address@hidden>
> Cc: address@hidden, address@hidden
> Date: Fri, 09 Mar 2012 22:54:53 +0900
> In article <address@hidden>, Eli Zaretskii <address@hidden> writes:
> > > (insert #x642 #x64C)
> > > (insert #x642 (propertize " " 'invisible t) #x64C)
> > This looks exactly identical to me (on MS-Windows), except that the
> > second one causes annoying behavior of cursor motion around the
> > inserted text.
> > Does it work for you on GNU/Linux?
> Yes.
> > If so, does it work for you to change
> > quail-insert-kbd-layout to use this trick in order to
> > separate the `lower' from the `upper' in the key cells?
> Yes.  But it depends on the font selected for arabic and the
> shaping engine for that font.  Some shapers display a glyph
> for an independent combining character with dotted circle (if
> the width of the glyph is zero).

It looks like Uniscribe on Windows, or at least its version supplied
with XP, doesn't live in peace with zero-width combining characters,
which is why I don't see the effect of inserting an invisible space.

> The better result is done by this:
> (insert #x642 (compose-string "\x64C" 0 1 "\t\x64C\t"))

Yes, that's what "C-u C-x =" does, and it works for me as well.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]