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 ...

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
___________________________________________________________________________________

Reply via email to