all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Wolfgang Jenkner <wjenkner@inode.at>
To: handa@gnu.org (K. Handa)
Cc: 21846@debbugs.gnu.org, mhd@yv.org, b.riefenstahl@turtle-trading.net
Subject: bug#21846: 25.0.50; emacs hebrew script bidi nikud rendering bug
Date: Fri, 18 Mar 2016 16:56:23 +0100	[thread overview]
Message-ID: <85pourn5g9.fsf@inode.at> (raw)
In-Reply-To: <87y4eag3s8.fsf@ubuntu.i-did-not-set--mail-host-address--so-tickle-me>

On Sun, Jan 03 2016, K. Handa wrote:

> I committed changes to enable ftfont-base font-backend to handle wider
> range of combining characters for non-OTF fonts.  So, hebrew
> diacticicals should be rendered by "Aharoni CLM" font.
>
> Could you verify it?

These changes (536f48e, 9835757, resp. the backports to emacs-25, viz.
4a3db0f, ad879b7) seem to break rendering of some Indic scripts.
Conjuncts are not composed anymore but rendered with virāma instead.
E.g., please see the Hindi entry of the HELLO file.

Apparently, the reason is this change

-      if (0x300 <= c1 && c1 <= 0x36F)
+      if (CHAR_HAS_CATEGORY (c1, '^'))

as, say, "DEVANAGARI SIGN VIRAMA" is excluded by the old condition but
included by the new one:

(category-set-mnemonics (char-category-set ?\u094d))
=> "^i"





  parent reply	other threads:[~2016-03-18 15:56 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-06 22:29 bug#21846: 25.0.50; emacs hebrew script bidi nikud rendering bug Mark H. David
2015-11-07  0:12 ` bug#21846: Additional Info re: bug#21846 (25.0.50; emacs hebrew script bidi nikud rendering bug) Mark David
2015-11-07  8:59 ` bug#21846: 25.0.50; emacs hebrew script bidi nikud rendering bug Eli Zaretskii
2015-11-08  0:49   ` Mark David
2015-11-07 17:44 ` Benjamin Riefenstahl
2015-11-07 17:58   ` Eli Zaretskii
2015-11-07 19:24     ` Benjamin Riefenstahl
2015-11-08  0:56       ` Mark David
2015-11-08 16:21         ` Benjamin Riefenstahl
2015-11-28 19:33       ` Benjamin Riefenstahl
2015-11-29 22:59         ` Mark David
2015-11-30 17:22           ` Benjamin Riefenstahl
2015-11-30 23:02             ` Benjamin Riefenstahl
2015-12-01 14:52               ` Benjamin Riefenstahl
2015-12-10 23:15               ` Benjamin Riefenstahl
2015-12-11  2:36                 ` Mark H. David
2015-12-18 13:49                   ` K. Handa
2016-01-03 12:03                     ` K. Handa
2016-01-10 20:21                       ` Mark H. David
2016-01-12 16:38                       ` Benjamin Riefenstahl
2016-01-22 12:46                         ` K. Handa
2016-01-22 13:46                           ` Eli Zaretskii
2016-03-18 15:56                       ` Wolfgang Jenkner [this message]
2016-03-21 14:56                         ` handa
2016-03-21 19:05                           ` Wolfgang Jenkner
2016-03-25  9:42                             ` Eli Zaretskii
2016-03-25 10:01                               ` Mark H. David
2016-03-27 11:51                                 ` handa
2015-12-05 12:55             ` K. Handa
2015-12-06 18:28               ` Mark David
2015-12-07  3:05                 ` Richard Stallman
2015-12-07 13:45                 ` K. Handa
2015-12-07 16:24               ` Benjamin Riefenstahl

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

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

  git send-email \
    --in-reply-to=85pourn5g9.fsf@inode.at \
    --to=wjenkner@inode.at \
    --cc=21846@debbugs.gnu.org \
    --cc=b.riefenstahl@turtle-trading.net \
    --cc=handa@gnu.org \
    --cc=mhd@yv.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.