From: Ulrike Fischer <news3@nililand.de>
To: ntg-context@ntg.nl
Subject: Re: Problems with ttc-fonts
Date: Fri, 29 Apr 2016 11:25:29 +0200 [thread overview]
Message-ID: <p8lcffxwfg6g.dlg@nililand.de> (raw)
In-Reply-To: <bb0307fa-8512-98c7-1f63-93fa700c7e00@wxs.nl>
Am Fri, 29 Apr 2016 10:37:51 +0200 schrieb Hans Hagen:
>> Is is normal that glyph of ttc-fonts have no name data? If yes how
>> should one do substituations in such fonts?
>
> you can use the unicode number instead (unless i made a mistake)
["1"] = 46 works, but as names are easier to handle I'm still
interested to know why cambria doesn't have them.
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___________________________________________________________________________________
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:[~2016-04-29 9:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 7:51 Ulrike Fischer
2016-04-29 8:37 ` Hans Hagen
2016-04-29 9:25 ` Ulrike Fischer [this message]
2016-05-01 7:48 ` 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=p8lcffxwfg6g.dlg@nililand.de \
--to=news3@nililand.de \
--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).