GNU bug report logs - #55319
28.1.50; Abugida not rendered correctly (MacOS)

Previous Next

Package: emacs;

Reported by: Kai Ma <justksqsf <at> gmail.com>

Date: Sun, 8 May 2022 16:23:01 UTC

Severity: wishlist

Found in version 28.1.50

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Kai Ma <justksqsf <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 55319 <at> debbugs.gnu.org
Subject: bug#55319: 28.1.50; Abugida not rendered correctly (MacOS)
Date: Mon, 9 May 2022 09:43:48 +0800
> On May 9, 2022, at 00:57, Eli Zaretskii <eliz <at> gnu.org> wrote:
> 
> Emacs doesn't OOTB support scripts whose characters are not in
> Unicode.  When characters are not in Unicode, their properties and
> attributes aren't known, unless someone tells Emacs what they are.

That was my thought, too. However, I don’t think this is the root cause in this case.

1. Other applications (including Web browsers and the native GUI toolkit) render 
  the text just fine. This makes me believe the font file itself contains enough information.

2. Emacs also discovers some glyphs should be composed, e.g. intonation marks (e.g. #xed8c), 
  but not the vowels. I don’t know why this happens. I just tried copy character properties 
  from these good ones. It didn’t work.


But in general, this could just be Emacs not fully supporting OpenType features.





This bug report was last modified 3 years and 15 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.