From: Stef Schoonderwoerd <saschoonderwoerd@gmail.com>
To: ntg-context@ntg.nl
Subject: non-unicode glyphs in ttf fonts
Date: Tue, 21 Jun 2011 10:03:14 +0200 [thread overview]
Message-ID: <BANLkTin=yAg=Zj84MxCrHv5hwKd2EEhgOQ@mail.gmail.com> (raw)
Dear all,
My last question concerning feature files has been resolved, my
feature files now work fine. But there is one problem that still
remains. The standard ligatures in the font I use (Andron Mega Corpus)
work fine when approached by name in the feature file (some of them
are in the PUA here); However, other ligatures, notably Th, do not
work in stable nor beta. When I run context mkiv and it calls on e.g.
the Th ligature, i get "!LuaTeX error (file:(...)): Invalid glyph
index (gid ...). I tested it on palatino linotype which does the same.
Interestingly, the gid that luatex says is invalid is always the one
after the last glyph in the font (For palatino linotype, 1328; for
Andron Mega Corpus, 5486). In Andron Mega Corpus, I furthermore tested
all the ligatures that had a unicode codepoint (PUA) and they all work
when referenced by name. All those that do not, however, fail to work.
What is going on here?
Working on Mac OS X 10.6.7, btw. Some help is greatly appreciated.
Kind regards,
Stef Schoonderwoerd
___________________________________________________________________________________
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:[~2011-06-21 8:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 8:03 Stef Schoonderwoerd [this message]
2011-06-21 8:15 ` Hans Hagen
[not found] ` <BANLkTikvrRZYVaA+8D3VNt8vfytiUAMKpQ@mail.gmail.com>
2011-06-21 11:19 ` Hans Hagen
2011-06-21 11:34 ` Stef Schoonderwoerd
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='BANLkTin=yAg=Zj84MxCrHv5hwKd2EEhgOQ@mail.gmail.com' \
--to=saschoonderwoerd@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).