From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: context manuals -- absence of \definefontfamily
Date: Wed, 5 Jan 2022 09:01:18 +0100 [thread overview]
Message-ID: <cd2bf79b-17b9-69d4-904d-d6ada2890739@xs4all.nl> (raw)
In-Reply-To: <YdTFDz9j90zm4Kkn@phare.normalesup.org>
On 1/4/2022 11:07 PM, Arthur Rosendahl wrote:
> On Mon, Jan 03, 2022 at 11:16:46PM +0100, Hans Hagen via ntg-context wrote:
>> Because Wolfgang has to write a chapter (or a MyWay document) and we're all
>> mostly volunteers so ...
>
> Youssef has got a point, though: \definefontfamily should perhaps be
> given a tiny bit better treatment on the wiki. I agree with him that
> https://wiki.contextgarden.net/Use_the_fonts_you_want seems like the
> best place to mention it, and even think that all of the last section
> could be rewritten using \definefontfamily instead of a typescript
> definition (which can be moved elsewhere, it obviously doesn’t need to
> be deleted from the wiki entirely). But I wouldn’t like to disturb the
> good work that Garulfo did when he overhauled the wiki, hence if you’re
> around, Garulfo, perhaps you could comment on that?
a note:
basically we have 3 ways to define a font (collection):
- selectfont: works find when fonts have 'correct' names and come in
consistent 'sets' (which is not always the case)
- typescripts: for long term stable style usage this is best because one
uses filenames and can even rename font files then so that updates don't
clash (typescripts can be in styles or in separate files)
- single font: for specific usage, like special fonts or titling;
definition by name or file or spec but probably most oiften by file
(just to be sure); although one can use abstraction by name this methoid
is not used for collections
mechanisms like fallbacks work for all but may need additional definitions
design siszes can complicate matters but there are no many
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
___________________________________________________________________________________
next prev parent reply other threads:[~2022-01-05 8:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 20:41 Youssef Cherem via ntg-context
2022-01-03 22:16 ` Hans Hagen via ntg-context
2022-01-03 23:21 ` Aditya Mahajan via ntg-context
2022-01-04 22:07 ` Arthur Rosendahl via ntg-context
2022-01-05 8:01 ` Hans Hagen via ntg-context [this message]
[not found] <mailman.1.1641294002.10048.ntg-context@ntg.nl>
2022-01-04 12:53 ` Jeong Dal via ntg-context
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=cd2bf79b-17b9-69d4-904d-d6ada2890739@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.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).