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: Tue, 24 Mar 2015 19:03:38 +0200 [thread overview]
Message-ID: <834mpaqqdx.fsf@gnu.org> (raw)
In-Reply-To: <20150324082828.6bad0649@JRWUBU2>
> Date: Tue, 24 Mar 2015 08:28:28 +0000
> From: Richard Wordingham <richard.wordingham@ntlworld.com>
> Cc: 20173@debbugs.gnu.org
>
> On Tue, 24 Mar 2015 05:42:18 +0200
> Eli Zaretskii <eliz@gnu.org> wrote:
>
> > If the setting of composition
> > rules for Arabic is not the culprit, then what is? AFAIK, there are
> > no rules that guide Emacs's shaping except what's in
> > composition-function-table. Beyond that, the only other factor is the
> > font backend and how it shapes glyphs given the chunks of text Emacs
> > presents to it.
>
> The font backend on Unixy systems consists of three components - m17n
> (shaping control), libotf (OTL look-up implementation) and Freetype
> (glyph rendering). The glue between them is in Emacs,
> most relevantly in function ftfont_drive_otf() in ftfont.c.
>
> My analysis of the problem, which could quite easily be wrong, is as
> follows. To control the positioning of marks for the mark2ligature
> lookup, it is necessary to record in some fashion which component of
> the ligature a mark applies to. I cannot see this information being
> stored. The information should be generated and used by libotf, but
> needs to be stored between callbacks of ftfont_drive_otf() by m17n.
> (The initial settings are implicit in the sequence of codepoints.)
> Storing this information would, so far as I can see, require a change to
> ftfont_drive_otf().
So this means that on Windows this problem does not exist?
> You might want to first check whether composed Arabic is
> usable. Doesn't making each word a grapheme cluster makes editing
> unpleasant?
I don't know; I don't speak or write any of the languages that use the
Arabic script. I expect the users that do to come up and ask for
features they miss. We already allow deletion of single codepoints,
even when they are composed; we might as well provide similar features
for movement or whatever. But the requests (and, perhaps, even the
code) should come from people who actually use these scripts,
otherwise it's a sure way to white elephants and other similar
creatures.
Thanks.
next prev parent reply other threads:[~2015-03-24 17:03 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834mpaqqdx.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 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.