On Fri, Sep 18, 2020 at 4:17 PM Hans Hagen <j.ha...@xs4all.nl> wrote:

> On 9/18/2020 11:23 AM, Christoph Reller wrote:
> > Dear List,
> >
> > I have the following MWE:
> >
> > \definefontsynonym[ZapfDingbats][file:ZapfDingbats][features=dingbats]
> > \usemodule [fnt-10]
> > \starttext
> > (1) \getglyphdirect{ZapfDingbats}{61491}\crlf % MKIV log: char 
> > (U+0F033) in font 'ZapfDingbats-4' with id 8: missing
> > (2) \getglyphdirect{ZapfDingbats}{983059}     % LMTX log: char 󰀓
> > (U+F0013) in font 'ZapfDingbats-4' with id 8: missing
> > \ShowCompleteFont{name:ZapfDingbats}{14pt}{1}
> > \stoptext
> >
> Dingbats are old school t1 without proper names so we can't use
> unicodes. However, there is a goodie that should do that so that in
> principle it should work with unicodes but there is some interference
> going on (i'll look at that)
>
> For nwo access by 'name' or 'index' (these are kind of stable for such
> an old font):
>
>       n:a34  : \getglyph{ZapfDingbats}{\tochar{n:a34}}  \par
>       n:a35  : \getglyph{ZapfDingbats}{\tochar{n:a35}}  \par
>       i:48   : \getglyph{ZapfDingbats}{\tochar{i:48}}   \par
>       i:49   : \getglyph{ZapfDingbats}{\tochar{i:49}}   \par
>       n:a104 : \getglyph{ZapfDingbats}{\tochar{n:a104}} \par
>       n:a105 : \getglyph{ZapfDingbats}{\tochar{n:a105}} \par
>
> Thank you Hans!

Access by glyph index with \tochar{i:19} works well for both MKIV and LMTX.
Access by name with \tochar{n:a39} does not work in LMTX with log
message: char ✓ (U+02713) in font 'ZapfDingbats-4' with id 8: missing. Also
\ShowCompleteFont does not report any glyph names in LMTX.

Cheers,
Christoph
___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Reply via email to