ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Pawel Urbanski via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: [NTG-context] Google's Roboto Flex font typescript and goodies definition.
Date: Tue, 18 Apr 2023 15:29:39 +0200	[thread overview]
Message-ID: <9618f51a-9849-13f5-e4bc-02e1cdc3727d@freedom.nl> (raw)
In-Reply-To: <CADUDiDEovGxyvEgFRH3oFwRHr__7tEs6vX4VyyBQT+X5ckZ7=w@mail.gmail.com>

On 4/18/2023 12:37 PM, Pawel Urbanski via ntg-context wrote:
> Dear Everyone,
> Following my attempts to create and learn Context's ways to manage 
> fonts, I would like to ask about the following:
> 
> I've created the structure for fonts in texmf-local folder and after 
> running scripts they are listed. The output for Roboto Flex is as follows:
> identifier                          familyname   fontname           
>   filename         subfont   instances
> 
> robotoflex                          robotoflex   robotoflexregular   
> robotoflex.ttf             thin extralight light regular medium semibold 
> bold extrabold black extrablack thinitalic extralightitalic lightitalic 
> italic mediumitalic semibolditalic bolditalic extrabolditalic 
> blackitalic extrablackitalic
> 
> What is the proper way to use family name or font name to create a 
> typescript file and a goodies file to take advantage of optical sizes. 
> Google's Roboto Flex is an upgraded Roboto as a variable font.
> 
> I know that this topic has been discussed many times and I've read the 
> fonts manual but still have these questions. Most of the examples are 
> rather ready solutions or templates but not always cover ways how to 
> figure out values from scratch and how they correspond.
all these naames and combining them into 'regular-bold' pairs is pretty 
much a visual thing as these names are not used consistently; when you 
just use four fonts, a simple few line tyopescript will do (no need to 
make an imp file, just put it in your style)

(variable fonts is not really improving this)

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:[~2023-04-18 13:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-18 10:37 Pawel Urbanski via ntg-context
2023-04-18 13:29 ` Hans Hagen via ntg-context [this message]
2023-04-18 14:14   ` Pawel Urbanski via ntg-context
2023-04-18 13:52 ` Pawel Urbanski via ntg-context
2023-04-18 15:39   ` Hans Hagen via ntg-context
2023-04-19 14:06     ` Pawel Urbanski 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=9618f51a-9849-13f5-e4bc-02e1cdc3727d@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).