[NTG-context] Output problem with nodes.toutf utility function(latest beta 02.26.2019)

Hans Hagen j.hagen at xs4all.nl
Fri Mar 1 01:14:55 CET 2019


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
-----------------------------------------------------------------


More information about the ntg-context mailing list