unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Richard Wordingham <richard.wordingham@ntlworld.com>
Cc: 20173@debbugs.gnu.org
Subject: bug#20173: 24.4; Rendering misallocates combining marks on ligatures
Date: Mon, 23 Mar 2015 17:38:52 +0200	[thread overview]
Message-ID: <83wq27raer.fsf@gnu.org> (raw)
In-Reply-To: <20150323010626.530d3395@JRWUBU2>

> Date: Mon, 23 Mar 2015 01:06:26 +0000
> From: Richard Wordingham <richard.wordingham@ntlworld.com>
> 
> When a ligature of two base characters has two combining marks on the
> first component but none on the second, the second combining mark is
> rendered as though it applied to the second component. A good example
> is the Arabic sequence لَّا (lam, shadda, fatha, alef - <U+0644, U+0651,
> U+064E, U+0627), where the shadda is rendered on the lam part of
> lam-alif ligature and the fatha on the alif part.  This problem is not
> restricted to right-to-left scripts; I encountered the problem when
> debugging left-to-right rendering.  Lam-alif is one of the most
> reliably generated ligatures bearing marks on different components.

Is it possible that some rule(s) are missing from the end of
lisp/language/misc-lang.el?  Could you please take a look and see if
something needs to be fixed/added in how we set up the compositions
for Arabic?

Thanks.





  reply	other threads:[~2015-03-23 15:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-23  1:06 bug#20173: 24.4; Rendering misallocates combining marks on ligatures Richard Wordingham
2015-03-23 15:38 ` Eli Zaretskii [this message]
2015-03-23 22:41   ` Richard Wordingham
2015-03-24  3:42     ` Eli Zaretskii
2015-03-24  8:28       ` Richard Wordingham
2015-03-24 17:03         ` Eli Zaretskii
2015-03-24 20:22           ` Richard Wordingham
2015-03-27  9:04           ` Richard Wordingham
2015-03-27  9:54             ` Eli Zaretskii
2020-08-17 22:45               ` Stefan Kangas

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=83wq27raer.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=20173@debbugs.gnu.org \
    --cc=richard.wordingham@ntlworld.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).