From: Christoph Reller <christoph.reller@gmail.com>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ZapfDingbats Unicode differences MKIV vs LMTX
Date: Tue, 22 Sep 2020 07:19:50 +0200 [thread overview]
Message-ID: <CAO8LnPG30EO9Mx8MQKjeyxoC3hApG30HVwF_6DwsaN5hsUo-Kg@mail.gmail.com> (raw)
In-Reply-To: <ff4b944c-e94a-b3c1-a0bc-980f0e7bbd67@xs4all.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1133 bytes --]
On Mon, Sep 21, 2020 at 3:27 PM Hans Hagen <j.hagen@xs4all.nl> wrote:
> On 9/21/2020 2:55 PM, Christoph Reller wrote:
>
> > \definefontsynonym[ZapfDingbats][file:ZapfDingbats][features=dingbats]
>
> I don't know what the previous line does ... but it works ok here when
> you remove it.
This line loads the font from a file ZapfDingbats.ttf. Without this line I
get no check marks in the output and the following log messages:
fonts > defining > font with asked name 'uzdr' is not found using
lookup 'file'
fonts > defining > unknown font 'uzdr', loading aborted
Correct me if I am wrong, but there does not seem to be a font file named
uzdr* in the distribution tree.
> \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.)
>
[-- Attachment #1.2: Type: text/html, Size: 1739 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
___________________________________________________________________________________
next prev parent reply other threads:[~2020-09-22 5:19 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
2020-09-21 12:55 ` Christoph Reller
2020-09-21 13:27 ` Hans Hagen
2020-09-22 5:19 ` Christoph Reller [this message]
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=CAO8LnPG30EO9Mx8MQKjeyxoC3hApG30HVwF_6DwsaN5hsUo-Kg@mail.gmail.com \
--to=christoph.reller@gmail.com \
--cc=j.hagen@xs4all.nl \
--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).