unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: johnw@newartisans.com, handa@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: how reliable is rendering of complex scripts?
Date: Tue, 06 Oct 2015 19:17:35 +0300	[thread overview]
Message-ID: <838u7gx97k.fsf@gnu.org> (raw)
In-Reply-To: <83wpv1xgrc.fsf@gnu.org>

> Date: Mon, 05 Oct 2015 22:22:15 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: emacs-devel@gnu.org
> 
> > The ZWNJ seems to work fine, but the ZWJ does not produce the behavior
> > documented here:
> > 
> >     http://persian.nmelrc.org/persianword/zwj.htm
> > 
> > That is, ZWJ does not extend the heh into a "heh do chesm" (heh with two
> > eyes), it just adds space before or after the final-form (circular) heh.
> 
> I tried to fix that, but I'm not sure it helped.  Maybe I simply don't
> understand how to write entries for composition-function-table.
> Perhaps Handa-san could help.

I found a subtle bug in the Emacs bidi reordering engine that affected
this.  After fixing it, the display is more reasonable in these cases.
The only remaining problem is display of sequences where the
zero-width controls are not between 2 Arabic letters, e.g. a u+0647
followed by ZWJ and a newline, in a left-to-right paragraph, a
relatively rare situation (it does work correctly in R2L paragraphs).
The special requirements for treating ZWJ and ZWNJ during the bidi
reordering are hard to implement, and the advice in the UBA is
incompatible with the design of the Emacs display engine.  I will have
to think about this some more.

One thing that still bothers me is that even though the shaping of the
Arabic letters is clearly affected by ZWJ and ZWNJ after the fix, the
"C-u C-x =" command doesn't say there was a character composition
there.  Perhaps Handa-san could explain why is that.  Is it a bug?



      reply	other threads:[~2015-10-06 16:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02  5:39 how reliable is rendering of complex scripts? Werner LEMBERG
2015-10-02  7:30 ` Eli Zaretskii
2015-10-04  4:39   ` Werner LEMBERG
2015-10-04  7:07     ` Eli Zaretskii
2015-10-04  8:09       ` Werner LEMBERG
2015-10-04  9:12         ` Eli Zaretskii
2015-10-04  9:40           ` Werner LEMBERG
2015-10-04  9:57             ` Eli Zaretskii
2015-10-04 18:06       ` John Wiegley
2015-10-04 19:45         ` Eli Zaretskii
2015-10-04 21:43           ` John Wiegley
2015-10-05  6:05             ` Eli Zaretskii
2015-10-05 18:18               ` John Wiegley
2015-10-05 19:22                 ` Eli Zaretskii
2015-10-06 16:17                   ` Eli Zaretskii [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=838u7gx97k.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=handa@gnu.org \
    --cc=johnw@newartisans.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).