From: Ulrike Fischer <news3@nililand.de>
To: ntg-context@ntg.nl
Subject: decomposed and precomposde glyphs
Date: Thu, 23 Feb 2017 11:58:05 +0100 [thread overview]
Message-ID: <tmggqdst95pj.dlg@nililand.de> (raw)
When using input like the following with xetex then harfbuzz kicks
in and one would always get the good looking precomposed U+1EA0 for
the A and the decomposed B+U+0323 for the B.
With context (and lualatex) one get a rather bad looking -- as the
dot is misplaced -- output for the A^^^^0323 input and no output at
all for ^^^^1e04.
As the coverage for precomposed glyphs varies a lot across fonts
this is rather a nuisance. Is there a way to get the fontloader
(also the one used by luaotfload) to do a similar substituation as
done by harfbuzz?
\starttext
\catcode`\^= 7
Ạ A^^^^0323 %decomposed input -> U+1EA0 with xetex
Ạ ^^^^1ea0 %precomposed input
Ḅ B^^^^0323 %decomposed input
^^^^1e04 %precomposed input -> B+U+0323 with xetex
\stoptext
(I added the ^^-notation to avoid problems with copy&paste)
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2017-02-23 10:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 10:58 Ulrike Fischer [this message]
2017-02-23 12:19 ` Hans Hagen
2017-02-23 12:35 ` Ulrike Fischer
2017-02-23 13:08 ` Hans Hagen
2017-02-23 14:05 ` Ulrike Fischer
2017-02-23 15:10 ` Hans Hagen
2017-02-23 15:12 ` Ulrike Fischer
2017-02-23 15:55 ` Hans Hagen
2017-02-23 17:26 ` Ulrike Fischer
2017-02-23 17:41 ` Hans Hagen
2017-02-23 17:47 ` Ulrike Fischer
2017-02-23 17:45 ` luigi scarso
2017-02-23 17:50 ` Ulrike Fischer
2017-02-23 18:28 ` luigi scarso
2017-02-23 17:47 ` Hans Hagen
2017-02-23 16:20 ` Arthur Reutenauer
2017-02-24 9:35 ` Ulrike Fischer
2017-02-24 11:52 ` Hans Hagen
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=tmggqdst95pj.dlg@nililand.de \
--to=news3@nililand.de \
--cc=ntg-context@ntg.nl \
/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.
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 NNTP newsgroup(s).