From: Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Henning Hraban Ramm <texml@fiee.net>
Subject: Re: Additional font variants
Date: Mon, 2 Aug 2021 00:35:37 +0200 [thread overview]
Message-ID: <27BAEA4F-0F42-4865-BFCB-72EFAB16B171@fiee.net> (raw)
In-Reply-To: <59de1e6c-d318-3e78-0ff6-aba64cef6e68@xs4all.nl>
> Am 01.08.2021 um 22:14 schrieb Hans Hagen via ntg-context <ntg-context@ntg.nl>:
>>> Is this a limitation in ConTeXt, or what did I wrong?
>> The handwritten and calligraphic style are limited to upright alternatives. I can only speculate why this is the case but I guess Hans owns no font families where this is necessary (e.g. Lucida Bright has only one file for handwriting and calligraphy).
>> Adding additional alternatives to both styles is possible but the included typescripts (e.g. for lucida bright ot) have to be checked and fixed.
> indeed the only reason is that lucida had handwritten and calligraphy as part of the whole package
>
> nowadays i'd just define a separate typeset set for it (same for narrow or light or ...)
Thank you for explaining!
So I know what to do.
Hraban
___________________________________________________________________________________
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:[~2021-08-01 22:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-01 17:33 Henning Hraban Ramm via ntg-context
2021-08-01 18:19 ` Wolfgang Schuster via ntg-context
2021-08-01 20:14 ` Hans Hagen via ntg-context
2021-08-01 22:35 ` Henning Hraban Ramm 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=27BAEA4F-0F42-4865-BFCB-72EFAB16B171@fiee.net \
--to=ntg-context@ntg.nl \
--cc=texml@fiee.net \
/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).