ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: Non-standard font alternatives
Date: Tue, 13 Dec 2022 09:53:19 +0100	[thread overview]
Message-ID: <de7e1acd-809e-0625-c2d6-de10a710ccf2@freedom.nl> (raw)
In-Reply-To: <3AA1AF9A-D024-44A5-A568-2A1C14900BE5@icloud.com>

On 12/13/2022 9:15 AM, Matthew McCabe via ntg-context wrote:
> Hi list,
> 
> I'm looking to import a font with medium and light weights (in this case 
> Roboto) and define font alternatives so one can quickly switch to light 
> text just as one would switch to bold text. There is a stackexchange 
> answer from Wolfgang 
> (https://tex.stackexchange.com/questions/303648/context-font-weights 
> <https://tex.stackexchange.com/questions/303648/context-font-weights>) 
> which details a solution to this problem for ConTeXt MkIV but despite my 
> best efforts I haven't been able to get things to work for me. There is 
> the Roboto typescript example on ConTeXt garden but it isn't exactly 
> what I'm looking for as for the document I'm making I would prefer to be 
> able to treat the font weights as alternatives rather than separate 
> families since I will be switching often.
take a look at type-imp-plex.mkiv (just remove the \s! in your case)

basically you define two typefaces: normal and light and then just 
switch between these, as in:

at the top of your document you say

\usebodyfont[plex]       % preloads
\usebodyfont[plex-light] % preloads

\setupbodyfont[plex]     % enables main font

and after that

{\switchtobodyfont[plex-light] .... }

will do a consistent switch

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

  reply	other threads:[~2022-12-13  8:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13  8:15 Matthew McCabe via ntg-context
2022-12-13  8:53 ` Hans Hagen via ntg-context [this message]
2022-12-14 10:49   ` Matthew McCabe via ntg-context
2023-01-06  7:55     ` Hans Hagen via ntg-context
2023-04-19 14:53       ` [NTG-context] " Pawel Urbanski via ntg-context
2023-04-19 16:52         ` Henning Hraban Ramm via ntg-context
2023-04-19 18:02           ` Pawel Urbanski via ntg-context
2023-04-19 19:24         ` Henning Hraban Ramm via ntg-context
2023-04-19 21:57           ` Pawel Urbanski via ntg-context
2023-04-20 21:34           ` Pawel Urbanski via ntg-context
2022-12-14 18:02 ` Wolfgang Schuster 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=de7e1acd-809e-0625-c2d6-de10a710ccf2@freedom.nl \
    --to=ntg-context@ntg.nl \
    --cc=j.hagen@freedom.nl \
    /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).