unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Werner LEMBERG <wl@gnu.org>
Cc: Kenichi Handa <handa@gnu.org>, emacs-devel@gnu.org
Subject: Re: how reliable is rendering of complex scripts?
Date: Fri, 02 Oct 2015 10:30:17 +0300	[thread overview]
Message-ID: <83pp0x7mnq.fsf@gnu.org> (raw)
In-Reply-To: <20151002.073900.472512461.wl@gnu.org>

(CC'ing Handa-san, who wrote most of the relevant display code in
Emacs, and also the m17n shaping engine libraries.)

> Date: Fri, 02 Oct 2015 07:39:00 +0200 (CEST)
> From: Werner LEMBERG <wl@gnu.org>
> 
> I wonder how reliable emacs displays complex scripts like Devanagari
> or Arabic.

AFAIK, no one has ever performed a study about this, let alone
repeated it when the relevant standards changed.

> For example, the maintainers of the HarfBuzz library did extensive
> comparisons of the rendering results with the MS engine to iron out
> zillions of small buglets in OpenType handling.

At least on MS-Windows, Emacs uses the MS engine directly, so some of
similar buglets should not affect us on Windows.

> AFAIK, Emacs relies on the m17n libraries, at least on GNU/Linux (no
> idea about other environments), controlling the OpenType handling
> (partially?) with Lisp code

That is correct.  And while the shaping engines, like libm17n-flt and
Uniscribe, are beyond the scope of Emacs maintenance, the supporting
Lisp and C code is on our table.  However, we currently lack a
maintainer in that area (have been lacking for a long time), so I
guess we are not up to speed with the latest developments.  I'm
talking first and foremost about the definitions of
character-composition patterns, which tell Emacs which sequences of
characters should be rendered as a single grapheme cluster.  There's a
lot to do in this area for various languages.

> are there test suites to compare the results?

There's a test suite for bidirectional display, but it only tests the
reordering of characters for display, not the shaping.  There's
nothing else, AFAIK.  If you, or someone else, can work on adding one,
that'd be great.



  reply	other threads:[~2015-10-02  7:30 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 [this message]
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

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=83pp0x7mnq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=handa@gnu.org \
    --cc=wl@gnu.org \
    /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).