From: "Mattias Märka via ntg-context" <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: "Mattias Märka" <mattias@marka.ee>
Subject: Re: Best way to access casul fonts
Date: Mon, 30 Jan 2023 18:05:23 +0000 [thread overview]
Message-ID: <pu2LfFNg3mUyunDpKoUU-KzNVdxwc-Zg1ezr6lKIVX8rac4X1nflUNcYDQT_xCU_t64O9DkkCIBrCTkL21Dc0nUHyofic1NF5wzNzHYrJHw=@marka.ee> (raw)
In-Reply-To: <9cf45a82-9ae6-2a3e-7934-d38136d2c4b0@fiee.net>
Ha, good to know. Do you know what one should do instead?
Also, do you know why this is? It would be good to mention this on the wiki.
Mattias
------- Original Message -------
On Monday, January 30th, 2023 at 7:49 PM, Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl> wrote:
>
>
>
> Am 30.01.23 um 18:24 schrieb Mattias Märka via ntg-context:
>
> > \definefontstyle is still bugging me. I gather from previous threads that it should be possible to define a new font style for casual and use that via a font switch, but I cannot get this to work. I'm not sure this is still possible.
>
>
> No, it isn’t, I recently asked Hans.
>
> Hraban
>
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
>
> maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : https://www.pragma-ade.nl / http://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net
> ___________________________________________________________________________________
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-01-30 18:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 18:04 Mattias Märka via ntg-context
2023-01-23 18:42 ` Garulfo via ntg-context
2023-01-23 19:10 ` Pablo Rodriguez via ntg-context
2023-01-23 19:32 ` Mattias Märka via ntg-context
2023-01-24 7:41 ` Pablo Rodriguez via ntg-context
2023-01-29 18:07 ` Mattias Märka via ntg-context
2023-01-30 11:20 ` Pablo Rodriguez via ntg-context
2023-01-30 17:24 ` Mattias Märka via ntg-context
2023-01-30 17:49 ` Henning Hraban Ramm via ntg-context
2023-01-30 18:05 ` Mattias Märka via ntg-context [this message]
2023-01-30 20:10 ` Hans Hagen 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='pu2LfFNg3mUyunDpKoUU-KzNVdxwc-Zg1ezr6lKIVX8rac4X1nflUNcYDQT_xCU_t64O9DkkCIBrCTkL21Dc0nUHyofic1NF5wzNzHYrJHw=@marka.ee' \
--to=ntg-context@ntg.nl \
--cc=mattias@marka.ee \
/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).