context manuals -- absence of \definefontfamily
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.
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 -----------------------------------------------------------------
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
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? Best, Arthur
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 -----------------------------------------------------------------
participants (4)
-
Aditya Mahajan -
Arthur Rosendahl -
Hans Hagen -
Youssef Cherem