From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Joseph Canedo <josephcanedo@gmail.com>
Subject: Re: Output problem with nodes.toutf utility function(latest beta 02.26.2019)
Date: Fri, 1 Mar 2019 01:14:55 +0100 [thread overview]
Message-ID: <a61fb17b-7869-51e1-36e0-304dd853726e@xs4all.nl> (raw)
In-Reply-To: <5c785edd.1c69fb81.10bfa.6c48@mx.google.com>
On 2/28/2019 11:21 PM, Joseph Canedo wrote:
> Yes, that’s correct, and that’s what I see in pdf. When I use
> nodes.toutf I suspect that now output in log file is no longer
> decomposed in T + h chars but it’s the Unicode char corresponding to Th
> ligature which editor font does not have glyph for.
>
> Apparently in previous versions the fonts.hashes.characters lua
> structure used to store unicode of components of ligature (so unicode
> element was a lua table/array) and now its 1 single value.
>
> local fonthashes = fonts.hashes
>
> local chardata = fonthashes.characters
>
> local info = chardata[font][c]
>
> Before, info could have been a lua table (having 2 values, unicode for T
> and unicode for h) or a number (unicode for some single non ligature).
> Now it seems to be always 1 single value (unicode for Th).
>
> Is there anyway else I could get the decomposition of the ligature ?
i'll fix it .. a typo (side effect of optimization)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2019-03-01 0:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 16:53 Output problem with nodes.toutf utility function (latest " Joseph Canedo
2019-02-27 17:37 ` Rik Kabel
2019-02-28 22:21 ` Output problem with nodes.toutf utility function(latest " Joseph Canedo
2019-03-01 0:14 ` Hans Hagen [this message]
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=a61fb17b-7869-51e1-36e0-304dd853726e@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=josephcanedo@gmail.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).