ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan via ntg-context <ntg-context@ntg.nl>
To: Hans Hagen via ntg-context <ntg-context@ntg.nl>
Cc: Aditya Mahajan <adityam@umich.edu>
Subject: Re: context manuals -- absence of \definefontfamily
Date: Mon, 3 Jan 2022 18:21:18 -0500 (EST)	[thread overview]
Message-ID: <nycvar.YAK.7.78.908.2201031820150.10944@nqv-guvaxcnq> (raw)
In-Reply-To: <95593437-adc5-8549-dbe9-5760790e13eb@xs4all.nl>

[-- Attachment #1: Type: text/plain, Size: 1577 bytes --]

On Mon, 3 Jan 2022, Hans Hagen via ntg-context wrote:

> On 1/3/2022 9:41 PM, Youssef Cherem via ntg-context wrote:
> > Dear all,
> > 
> > I've come back to using Context and I noticed the nice manuals around -- 
> > but one thing I miss is \definefontfamily (and \definefallbackfamily).
> > 
> > There is info here:
> > https://wiki.contextgarden.net/Use_fonts_distributed_with_ConTeXt 
> > <https://wiki.contextgarden.net/Use_fonts_distributed_with_ConTeXt>
> > 
> > and then checking out the specific page: 
> > https://wiki.contextgarden.net/Command/definefontfamily 
> > <https://wiki.contextgarden.net/Command/definefontfamily>
> > 
> > It still baffles me that definefontfamily, though much simpler than 
> > typescripts (which is intimidating), is not mentioned in the beginner's 
> > manuals (unless I missed something) and neither is it given more 
> > prominence in the Wiki, although I often see it mentioned in the forums. 
> > Being used to fontspec's simplicity, I'd never use typescripts. It would 
> > help a lot, for example, to include a sample of "definefontfamily" in 
> > "Use any font you like".
> > 
> > Is there a reason why definefontfamily doesn't appear at all in the 
> > manuals (as far as I could see), which are rather comprehensive otherwise?
> 
> Because Wolfgang has to write a chapter (or a MyWay document) and we're 
> all mostly volunteers so ...

There is the talk that Wolfgang gave in this year's context meeting:

https://meeting.contextgarden.net/2021/talks/2021-09-23/definefontfamily.pdf

Aditya

[-- 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
___________________________________________________________________________________

  reply	other threads:[~2022-01-03 23:21 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 [this message]
2022-01-04 22:07   ` Arthur Rosendahl via ntg-context
2022-01-05  8:01     ` Hans Hagen via ntg-context
     [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=nycvar.YAK.7.78.908.2201031820150.10944@nqv-guvaxcnq \
    --to=ntg-context@ntg.nl \
    --cc=adityam@umich.edu \
    /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).