From: Rik Kabel <context@rik.users.panix.com>
To: ntg-context@ntg.nl
Subject: Re: Output problem with nodes.toutf utility function (latest beta 02.26.2019)
Date: Wed, 27 Feb 2019 12:37:20 -0500 [thread overview]
Message-ID: <508e667b-a529-3043-c776-40b065c93bc2@rik.users.panix.com> (raw)
In-Reply-To: <5c76c06a.1c69fb81.18d9d.c199@mx.google.com>
[-- Attachment #1.1: Type: text/plain, Size: 825 bytes --]
On 2/27/2019 11:53, Joseph Canedo wrote:
>
> Dear list,
>
> I use lua function nodes.toutf to print text being typeset in log
> output for debugging purposes etc… and I noticed output is now
> different for some characters/glyphs.
>
> I use EB Garamond font, which might explain.
>
> Before, for example output was :
>
> user > margin > margin box text Thareh.
>
> Now it is :
>
> user > margin > margin box text areh.
>
> The « Th » was replaced by some placeholder perhaps for unknown
> character?
>
> Please note that typeset text is not impacted, it seems correct.
>
> Joseph
>
The dlig feature for EBGaramond causes "Th" to be replaced by a
ligature. Look carefully at your typeset text and you will likely see
that the "T" and "h" are joined.
--
Rik
[-- Attachment #1.2: Type: text/html, Size: 2912 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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 prev parent reply other threads:[~2019-02-27 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 16:53 Joseph Canedo
2019-02-27 17:37 ` Rik Kabel [this message]
2019-02-28 22:21 ` Output problem with nodes.toutf utility function(latest " Joseph Canedo
2019-03-01 0:14 ` 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=508e667b-a529-3043-c776-40b065c93bc2@rik.users.panix.com \
--to=context@rik.users.panix.com \
--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).