all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kai Ma <justksqsf@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 55319@debbugs.gnu.org
Subject: bug#55319: 28.1.50; Abugida not rendered correctly (MacOS)
Date: Mon, 9 May 2022 09:43:48 +0800	[thread overview]
Message-ID: <F24FD1D8-535F-4645-B225-A296318569DD@gmail.com> (raw)
In-Reply-To: <83ilqgufm3.fsf@gnu.org>


> On May 9, 2022, at 00:57, Eli Zaretskii <eliz@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.






  reply	other threads:[~2022-05-09  1:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-08 11:45 bug#55319: 28.1.50; Abugida not rendered correctly (MacOS) Kai Ma
2022-05-08 16:57 ` Eli Zaretskii
2022-05-09  1:43   ` Kai Ma [this message]
2022-05-09  2:38     ` Eli Zaretskii
2022-05-11 15:43       ` Kai Ma
2022-05-11 16:12         ` Eli Zaretskii
2022-05-12  8:10         ` Robert Pluim
2022-05-12  8:26           ` Kai Ma
2022-05-12  8:36             ` Robert Pluim
2022-05-12  9:37               ` Eli Zaretskii
2022-05-12  9:42                 ` Robert Pluim
2022-05-12  9:54                   ` 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

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

  git send-email \
    --in-reply-to=F24FD1D8-535F-4645-B225-A296318569DD@gmail.com \
    --to=justksqsf@gmail.com \
    --cc=55319@debbugs.gnu.org \
    --cc=eliz@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 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.