ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Christoph Reller <christoph.reller@gmail.com>
Subject: Re: ZapfDingbats Unicode differences MKIV vs LMTX
Date: Fri, 18 Sep 2020 16:17:21 +0200	[thread overview]
Message-ID: <8278fd82-340d-00cb-ca51-a0a692f493ac@xs4all.nl> (raw)
In-Reply-To: <CAO8LnPGpsGa4Q7jYFM3LB-OWzhjsrGRv07AD22q7v99qdJ2KSQ@mail.gmail.com>

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
> 
> In MKIV, line (1) fails to output the requested glyph, while line (2) 
> produces a "check" (✓). In LMTX, line (2) fails and line (1) produces 
> the "check" (✓) . The output of "\ShowCompleteFont" reports differing 
> Unicodes for the same glyphs. Apparently the Unicodes for ZapfDingbats 
> have changed.
> 
> I would like to have a "check" (✓) in the output for both MKIV and LMTX. 
> Options:
> A) Is there a way to address the glyph in ZapfDingbats for both MKIV and 
> LMTX uniformly, e.g. by glyph index? (By glyph name does not seem to 
> work: MKIV reports glyph names, LMTX does not.)
> B) Is there a conditional that I can build into the source to 
> distinguish between MKIV and LMTX?
> C) Is there a font in the distribution for which I can have a 
> "check"-symbol in both MKIV and LMTX?
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

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-18 14:17 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 [this message]
2020-09-19  4:18   ` Christoph Reller
2020-09-19 10:04     ` Hans Hagen
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=8278fd82-340d-00cb-ca51-a0a692f493ac@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).