From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Taco Hoekwater <taco@elvenkind.com>
Cc: Hans Hagen <j.hagen@xs4all.nl>,
Benjamin Buchmuller <benjamin.buchmuller@gmail.com>
Subject: Re: Dangerous bends symbol in manfnt.afm accidentally chopped by LMTX?
Date: Sun, 2 Jan 2022 12:43:50 +0100 [thread overview]
Message-ID: <1c5b09ab-d692-39f6-25cc-9e9307cf1c4a@xs4all.nl> (raw)
In-Reply-To: <98599453-51E7-4E62-805E-C94008E896E8@gmail.com>
On 1/2/2022 11:30 AM, Benjamin Buchmuller via ntg-context wrote:
> Hi list,
>
> using this example from the wiki, the dbend symbol appears cropped on the left side on my machine (ConTeXt ver: 2021.12.10 11:41 LMTX fmt: 2021.12.14), but not on the ConTeXt live server? Any possible reasons?
>
> \definefontsynonym [bends] [file:manfnt.afm]
>
> \startsymbolset [Dangerous Bends]
> \definesymbol [dbend] [\resolvedglyphdirect{bends}{n:char_7e}]
> \definesymbol [lhdbend] [\resolvedglyphdirect{bends}{n:char_7f}]
> \stopsymbolset
>
> \setupsymbolset [Dangerous Bends]
>
> \starttext
> \symbol{dbend}\quad \symbol{lhdbend}
> \stoptext
The lhdbend renders funny anyway. Maybe Taco is willing to have a look
at it. It might actually make sense to make an opentype font and get rid
of the afm/pfb here.
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
___________________________________________________________________________________
prev parent reply other threads:[~2022-01-02 11:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.440.1641107345.1172.ntg-context@ntg.nl>
2022-01-02 10:30 ` Benjamin Buchmuller via ntg-context
2022-01-02 10:47 ` How to make \def accept block or buffer as part of (long) command argument Benjamin Buchmuller via ntg-context
2022-01-02 11:19 ` Hans Hagen via ntg-context
2022-01-02 13:14 ` Benjamin Buchmuller via ntg-context
2022-01-02 13:43 ` Hans Hagen via ntg-context
2022-01-02 17:06 ` Benjamin Buchmuller via ntg-context
2022-01-02 11:43 ` Hans Hagen via ntg-context [this message]
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=1c5b09ab-d692-39f6-25cc-9e9307cf1c4a@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=benjamin.buchmuller@gmail.com \
--cc=j.hagen@xs4all.nl \
--cc=taco@elvenkind.com \
/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).