From: Joseph Canedo <josephcanedo@gmail.com>
To: "ntg-context@ntg.nl" <ntg-context@ntg.nl>
Subject: (perhaps benign) difference in ebgaramond12-regular.tma after upgrade to 2016.07.30 00:26 beta
Date: Sat, 30 Jul 2016 14:10:19 +0200 [thread overview]
Message-ID: <579c9923.c997c20a.7c360.2906@mx.google.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 907 bytes --]
Hi Hans,
Perhaps completely benign, but a bit strange difference I’ve spotted (because I log the ligatures of the font I use).
After upgrade to 2016.07.30 00:26 I notice that 1 entry (only one which is a bit strange, because there are other similar entries in the description table which were not changed at all) in descriptions table in ebgaramond12-regular.tma (in tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otl/ directory) has changed from
[983766]={
["boundingbox"]=519,
["index"]=2684,
["name"]="ij.sc",
["unicode"]={ 105, 106 },
["width"]=570,
},
To (latest beta)
[983766]={
["boundingbox"]=519,
["index"]=2684,
["name"]="ij.sc",
["unicode"]=307, -- 307 is ij ligature whose unicode = { 105, 106 }
["width"]=570,
},
Is this expected at all ?
Thanks a lot
Best regards
Joseph Canedo
[-- Attachment #1.2: Type: text/html, Size: 3151 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2016-07-30 12:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-30 12:10 Joseph Canedo [this message]
2016-07-30 12:33 ` 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=579c9923.c997c20a.7c360.2906@mx.google.com \
--to=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).