From: "Jan Tosovsky" <j.tosovsky@email.cz>
To: "'mailing list for ConTeXt users'" <ntg-context@ntg.nl>
Subject: Re: [***SPAM***] Incorrect internal font processing
Date: Wed, 27 Nov 2013 23:09:09 +0100 [thread overview]
Message-ID: <36246.4704471224$1385590173@news.gmane.org> (raw)
In-Reply-To: <52966506.80606@wxs.nl>
On 2013-11-27 Hans Hagen wrote:
> On 11/27/2013 10:20 PM, Jan Tosovsky wrote:
> > On 2013-11-27 Hans Hagen wrote:
> >> On 11/27/2013 9:53 PM, Jan Tosovsky wrote:
> >>> On 2013-11-27 Hans Hagen wrote:
> >>>> On 11/27/2013 8:44 PM, Jan Tosovsky wrote:
> >>>>>
> >>>>> during my attempts to patch the Palatino's dotless 'i' I found
> >>>>> that this font is parsed incorrectly by ConTeXt.
> >>>>>
> >>>>> Comparing index/name info of individual glyphs in the font
> >>>>> software and resulting pala.tma file there is the following
> >>>>> difference:
> >>>>>
> >>>>> Index | Name - font | Name - tma
> >>>>> 1110 | dotlessi.smcp | i.sc (1)
> >>>>> 1170 | i.smcp | i.sc (2)
> >>>>>
> >>>>> The first one should have IMHO a different name, e.g. dotlessi.sc
> >>>>> (to keep conventions). The same name for two glyphs
> >>>>> might be dangerous.
> >>>>
>
> the fact that there are two i.sc in the font is suspicious ... best
> check the font in fontforge ... one never know what kind of things
> other programs do
Hmm, FontForge glyphs naming corresponds to what we can observe in the
ConTeXt (doubled i.sc). My previous analysis was based on FontLab. I am
confused now...
Jan
___________________________________________________________________________________
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 prev parent reply other threads:[~2013-11-27 22:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00b801ceeba9$0ee40cf0$2cac26d0$@tosovsky@email.cz>
2013-11-27 20:06 ` Hans Hagen
2013-11-27 20:53 ` Jan Tosovsky
[not found] ` <00c801ceebb2$bf8762b0$3e962810$@tosovsky@email.cz>
2013-11-27 20:56 ` Hans Hagen
2013-11-27 21:20 ` Jan Tosovsky
[not found] ` <00c901ceebb6$7bf1ea30$73d5be90$@tosovsky@email.cz>
2013-11-27 21:32 ` Hans Hagen
2013-11-27 22:09 ` Jan Tosovsky [this message]
[not found] ` <00cd01ceebbd$4c248090$e46d81b0$@tosovsky@email.cz>
2013-11-27 22:35 ` Jan Tosovsky
[not found] ` <00d401ceebc0$e9299df0$bb7cd9d0$@tosovsky@email.cz>
2013-11-28 9:33 ` Hans Hagen
[not found] ` <5296739d.6494420a.551e.0b07SMTPIN_ADDED_BROKEN@mx.google.com>
2013-12-01 9:21 ` Khaled Hosny
2013-12-01 11:05 ` Khaled Hosny
2013-12-08 20:19 ` Jan Tosovsky
[not found] ` <52a4d457.839d420a.34cb.0cc2SMTPIN_ADDED_BROKEN@mx.google.com>
2013-12-08 20:53 ` Khaled Hosny
2013-11-27 19:44 Jan Tosovsky
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='36246.4704471224$1385590173@news.gmane.org' \
--to=j.tosovsky@email.cz \
--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).