From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/103537 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Joseph Canedo Newsgroups: gmane.comp.tex.context Subject: Re: Output problem with nodes.toutf utility function(latest beta 02.26.2019) Date: Thu, 28 Feb 2019 23:21:20 +0100 Message-ID: <5c785edd.1c69fb81.10bfa.6c48@mx.google.com> References: <5c76c06a.1c69fb81.18d9d.c199@mx.google.com> <508e667b-a529-3043-c776-40b065c93bc2@rik.users.panix.com> Reply-To: mailing list for ConTeXt users Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3274996697429064861==" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="108037"; mail-complaints-to="usenet@blaine.gmane.org" To: mailing list for ConTeXt users Original-X-From: ntg-context-bounces@ntg.nl Thu Feb 28 23:21:47 2019 Return-path: Envelope-to: gctc-ntg-context-518@m.gmane.org Original-Received: from zapf.boekplan.nl ([5.39.185.232] helo=zapf.ntg.nl) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1gzU3m-000Rzz-LD for gctc-ntg-context-518@m.gmane.org; Thu, 28 Feb 2019 23:21:46 +0100 Original-Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 4ADBFF6871; Thu, 28 Feb 2019 23:21:22 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl Original-Received: from zapf.ntg.nl ([127.0.0.1]) by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Au67Xlri8tyD; Thu, 28 Feb 2019 23:21:20 +0100 (CET) Original-Received: from zapf.ntg.nl (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 37B87F68B7; Thu, 28 Feb 2019 23:21:20 +0100 (CET) Original-Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id CB08BF6871 for ; Thu, 28 Feb 2019 23:21:19 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl Original-Received: from zapf.ntg.nl ([127.0.0.1]) by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KxWmp9jH7oyI for ; Thu, 28 Feb 2019 23:21:19 +0100 (CET) Original-Received: from mail-wr1-f44.google.com (mail-wr1-f44.google.com [209.85.221.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by zapf.ntg.nl (Postfix) with ESMTPS id EED66F676E for ; Thu, 28 Feb 2019 23:21:18 +0100 (CET) Original-Received: by mail-wr1-f44.google.com with SMTP id l5so23743004wrw.6 for ; Thu, 28 Feb 2019 14:21:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:mime-version:to:from:subject:date:importance:in-reply-to :references; bh=yeOALkKee9JOcOlLXgOpmm/EJ0N8ogT6gji/hAB+UWk=; b=tcvdN3aR3xxYJopXVJOzjEQ+b+JNIB+PjsvU032gEc5gJmy3dYsaCIE8I8Wfr3U7O1 G8QCKtDQGOdSybdOgg+1gN1MTIRKFvpVWofT3HY4yW5TwPevm7hukJ1Visc4rDEbrG64 nvJU2NyhMMQ6gOrfXAgSjyjeKSzuhQN7mZdXdKQM5Y3rk6gsRXIwoKWGv0NP8gmOZ0qx R3H/r1hxTTIpatnjRnjWW5xHVE9jJTxrmjLOYv4hHjYnNv85EbdPw3t1KPnusMHYvLrd E3bJquyZAWVEsXNFgBWs57smP1Y1SI0iexgkzTnjAtN/DVAWF/MmmxA5YYr5dZRibexu RbQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:mime-version:to:from:subject:date :importance:in-reply-to:references; bh=yeOALkKee9JOcOlLXgOpmm/EJ0N8ogT6gji/hAB+UWk=; b=IzOaVxsWwIBMvbLBFeRtOG3ue8bQNe9rb6Zxm52rNyu8zyOyM5TAW+S6WqjUbHsprs kVLsDqyETA0agUKZU0OsQw3MZ8S6KYaamRQVrEPAMQl0FKltkfjOoA+kPU+ojuez+4jj LgbaAPwU8sW4MR0MDKctUNXc4/3mQlQiX3JdzOABNq9RpIoJLMR32X9hCuEDvm6UFRPB 78UV0WeUm2jAnaz6HkZyxEnLbkrJPiCmfzAYyVPjKwxsJnOQ8GBODQ931aomVDgL5izd XahIS1DyRMoEu4b6WFGqGdSR5TYPlxAQpTFUHzzWJX8T+5nsO+5Sw0FANsHYH22gNPdL xYkg== X-Gm-Message-State: APjAAAWlL2fbAg+m5wTFrGTXo6kpOR9NxUR0EeuNsMJXoHNAEF+dlKra pkc7qH4MF5eWn96AsiNBY0QGftxy X-Google-Smtp-Source: APXvYqzJf2iAmvxOc8K6DlLlKGf7v6qITQRlakrt3iGRRbKVVcf3B0lHRldN86z1OAJ1wo0pX2LWKg== X-Received: by 2002:adf:f78e:: with SMTP id q14mr1198884wrp.227.1551392478387; Thu, 28 Feb 2019 14:21:18 -0800 (PST) Original-Received: from ?IPv6:2a01:cb00:68e:300:1598:72c8:e7cf:9438? (2a01cb00068e0300159872c8e7cf9438.ipv6.abo.wanadoo.fr. [2a01:cb00:68e:300:1598:72c8:e7cf:9438]) by smtp.gmail.com with ESMTPSA id q5sm31414504wrn.43.2019.02.28.14.21.17 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 28 Feb 2019 14:21:17 -0800 (PST) Importance: normal X-Priority: 3 In-Reply-To: <508e667b-a529-3043-c776-40b065c93bc2@rik.users.panix.com> X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.26 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ntg-context-bounces@ntg.nl Original-Sender: "ntg-context" Xref: news.gmane.org gmane.comp.tex.context:103537 Archived-At: --===============3274996697429064861== Content-Type: multipart/alternative; boundary="_761F46C3-7780-4D0E-A963-F8A2CFC62FA6_" --_761F46C3-7780-4D0E-A963-F8A2CFC62FA6_ Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Yes, that=E2=80=99s correct, and that=E2=80=99s what I see in pdf. When I u= se nodes.toutf I suspect that now output in log file is no longer decompose= d in T + h chars but it=E2=80=99s the Unicode char corresponding to Th liga= ture which editor font does not have glyph for.=20 Apparently in previous versions the fonts.hashes.characters lua structure u= sed to store unicode of components of ligature (so unicode element was a lu= a table/array) and now its 1 single value. local fonthashes =3D fonts.hashes local chardata =3D fonthashes.characters local info =3D chardata[font][c] Before, info could have been a lua table (having 2 values, unicode for T an= d 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=C2=A0? Thanks, Joseph De=C2=A0: Rik Kabel Envoy=C3=A9 le=C2=A0:mercredi 27 f=C3=A9vrier 2019 18:37 =C3=80=C2=A0: ntg-context@ntg.nl Objet=C2=A0:Re: [NTG-context] Output problem with nodes.toutf utility funct= ion(latest beta 02.26.2019) On 2/27/2019 11:53, Joseph Canedo wrote: Dear list, =C2=A0 I use lua function nodes.toutf to print text being typeset in log output fo= r debugging purposes etc=E2=80=A6 and I noticed output is now different for= some characters/glyphs. I use EB Garamond font, which might explain. =C2=A0 Before, for example output was=C2=A0: =C2=A0 user=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 > ma= rgin > margin box text Thareh. =C2=A0 Now it is=C2=A0: =C2=A0 user=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 > ma= rgin > margin box text =F3=B0=80=99areh. =C2=A0 The =C2=AB=C2=A0Th=C2=A0=C2=BB was replaced by some =F3=B0=80=99 placeholde= r perhaps for unknown character? =C2=A0 Please note that typeset text is not impacted, it seems correct. =C2=A0 Joseph =C2=A0 The dlig feature for EBGaramond causes "Th" to be replaced by a ligature. L= ook carefully at your typeset text and you will likely see that the "T" and= "h" are joined. --=20 Rik --_761F46C3-7780-4D0E-A963-F8A2CFC62FA6_ Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="utf-8"

Yes, that=E2=80=99s correct, and that= =E2=80=99s what I see in pdf. When I use nodes.toutf I suspect that now out= put in log file is no longer decomposed in T + h chars but it=E2=80=99s the= Unicode char corresponding to Th ligature which editor font does not have = glyph for.

 

Apparently in previous versions the fonts.hashes.characters lua structur= e used to store unicode of components of ligature (so unicode element was a= lua table/array) and now its 1 single value.

=  

local fonthashes =3D fonts.hashes

<= p class=3DMsoNormal>local chardata =3D fonthashes.characters

 

local info =3D chardata= [font][c]

 

Before, info could have been a lua table (having 2 values, unicode for T a= nd unicode for h) or a number (unicode for some single non ligature). Now i= t 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=C3=A9 le :mercredi 27 f=C3=A9vri= er 2019 18:37
=C3=80 : ntg-context@ntg.nl
Objet :Re: [NTG-context] Output prob= lem with nodes.toutf utility function(latest beta 02.26.2019)

 

On 2/27/2019 11:53, Joseph Canedo wrote:

<= blockquote style=3D'margin-top:5.0pt;margin-bottom:5.0pt'>

Dear list,

 

I use lua function nodes.toutf to = print text being typeset in log output for debugging purposes etc=E2=80=A6 = and I noticed output is now different for some characters/glyphs.

I use EB Garam= ond font, which might explain.

 

= Before, for example output was :

 

user &n= bsp;          > margin >= margin box text Thareh.

 

Now it is :

 

user      = ;      > margin > margin box text 󰀙a= reh.

=  

The =C2=AB Th =C2=BB was replaced by some 󰀙 placeholder= perhaps for unknown character?

<= span style=3D'color:black'> 

Please note that typeset text is not impacted,= it seems correct.

 

Joseph

 

The dlig fea= ture for EBGaramond causes "Th" to be replaced by a ligature. Loo= k carefully at your typeset text and you will likely see that the "T&q= uot; and "h" are joined.

--
Rik

 

= --_761F46C3-7780-4D0E-A963-F8A2CFC62FA6_-- --===============3274996697429064861== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX18KSWYgeW91ciBxdWVzdGlvbiBpcyBvZiBpbnRlcmVz dCB0byBvdGhlcnMgYXMgd2VsbCwgcGxlYXNlIGFkZCBhbiBlbnRyeSB0byB0aGUgV2lraSEKCm1h aWxsaXN0IDogbnRnLWNvbnRleHRAbnRnLm5sIC8gaHR0cDovL3d3dy5udGcubmwvbWFpbG1hbi9s aXN0aW5mby9udGctY29udGV4dAp3ZWJwYWdlICA6IGh0dHA6Ly93d3cucHJhZ21hLWFkZS5ubCAv IGh0dHA6Ly9jb250ZXh0LmFhbmhldC5uZXQKYXJjaGl2ZSAgOiBodHRwczovL2JpdGJ1Y2tldC5v cmcvcGhnL2NvbnRleHQtbWlycm9yL2NvbW1pdHMvCndpa2kgICAgIDogaHR0cDovL2NvbnRleHRn YXJkZW4ubmV0Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCg== --===============3274996697429064861==--