ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: Christoph Reller <christoph.reller@gmail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ZapfDingbats Unicode differences MKIV vs LMTX
Date: Sat, 19 Sep 2020 12:04:40 +0200	[thread overview]
Message-ID: <08cb7911-5c43-82a9-9119-131f20d76272@xs4all.nl> (raw)
In-Reply-To: <CAO8LnPG4L3LOwk0uWqBgbVTj=8TcUs5TmHvR+BvCocdj5LOr0g@mail.gmail.com>

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:
>      > 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.
should be a bit better in yesterdays upload (i also changed the file 
name alias so that in pinciple unicode should work too)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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	other threads:[~2020-09-19 10:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-18  9:23 Christoph Reller
2020-09-18 14:17 ` Hans Hagen
2020-09-19  4:18   ` Christoph Reller
2020-09-19 10:04     ` Hans Hagen [this message]
2020-09-21 12:55       ` Christoph Reller
2020-09-21 13:27         ` Hans Hagen
2020-09-22  5:19           ` Christoph Reller
2020-09-22 11:51             ` Hans Hagen
2020-09-22 11:57               ` Taco Hoekwater

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=08cb7911-5c43-82a9-9119-131f20d76272@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=christoph.reller@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).