Output problem with nodes.toutf utility function (latest beta 02.26.2019)

Output problem with nodes.toutf utility function (latest beta 02.26.2019)

[Joseph Canedo]

[-- Attachment #1.1: Type: text/plain, Size: 560 bytes --]

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


[-- Attachment #1.2: Type: text/html, Size: 2347 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
___________________________________________________________________________________

Re: Output problem with nodes.toutf utility function (latest beta 02.26.2019)

[Rik Kabel]

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

Re: Output problem with nodes.toutf utility function(latest beta 02.26.2019)

[Joseph Canedo]

[-- Attachment #1.1: Type: text/plain, Size: 1873 bytes --]

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 ?

Thanks,
Joseph

De : Rik Kabel
Envoyé le :mercredi 27 février 2019 18:37
À : ntg-context@ntg.nl
Objet :Re: [NTG-context] Output problem with nodes.toutf utility function(latest beta 02.26.2019)

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: 5480 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
___________________________________________________________________________________

Re: Output problem with nodes.toutf utility function(latest beta 02.26.2019)

[Hans Hagen]

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
___________________________________________________________________________________