ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Youssef Cherem via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Youssef Cherem <ycherem@gmail.com>
Subject: context manuals -- absence of \definefontfamily
Date: Mon, 3 Jan 2022 17:41:54 -0300	[thread overview]
Message-ID: <CAPENqt0mEOv0m31ATk_3EbQ8W1w7pJ7irkRSh5iZYiEeY9xydg@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 978 bytes --]

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

and then checking out the specific page:
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?

All the best and thanks again for everything.

[-- Attachment #1.2: Type: text/html, Size: 2500 bytes --]

[-- 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 20:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03 20:41 Youssef Cherem via ntg-context [this message]
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
     [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=CAPENqt0mEOv0m31ATk_3EbQ8W1w7pJ7irkRSh5iZYiEeY9xydg@mail.gmail.com \
    --to=ntg-context@ntg.nl \
    --cc=ycherem@gmail.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).