Re: ZapfDingbats Unicode differences MKIV vs LMTX

[Christoph Reller <christoph.reller@gmail.com>]

[-- Attachment #1.1: Type: text/plain, Size: 2868 bytes --]

On Sat, Sep 19, 2020 at 12:04 PM Hans Hagen <j.hagen@xs4all.nl> wrote:

> On 9/19/2020 6:18 AM, Christoph Reller wrote:
> > On Fri, Sep 18, 2020 at 4:17 PM Hans Hagen <j.hagen@xs4all.nl
> > <mailto:j.hagen@xs4all.nl>> wrote:
> >
> >     On 9/18/2020 11:23 AM, Christoph Reller wrote:
> >
>  \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.
> should be a bit better in yesterdays upload (i also changed the file
> name alias so that in pinciple unicode should work too)


 Dear Hans,

Thank you for working on this. I have tried version 2020.09.20: Unicode
input works for the "Private Use Area" Unicodes reported in
\ShowCompleteFont. Such Unicodes are, however, not desirable. Moreover, in
MKIV, a Unicode U+2713 (Check Mark) in the input did produce the
ZapfDingbats check, e.g. as follows:

\definefontsynonym[ZapfDingbats][file:ZapfDingbats][features=dingbats]
\definefont[zapfdingbats][ZapfDingbats]
\starttext
{\zapfdingbats ✓}
\definedfont[name:ZapfDingbats]✓
\stoptext

I still get no check mark in the output PDF and a log message "char ✓
(U+02713) in font 'ZapfDingbats-4' with id 8: missing". Am I using the font
wrongly?
(This has not a high priority for me, because I have the unified access by
glyph index.)

Christoph

[-- Attachment #1.2: Type: text/html, Size: 3777 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________