From: Pawel Urbanski via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Pawel Urbanski <urbanski.pawel@gmail.com>
Subject: [NTG-context] Google's Roboto Flex font typescript and goodies definition.
Date: Tue, 18 Apr 2023 12:37:35 +0200 [thread overview]
Message-ID: <CADUDiDEovGxyvEgFRH3oFwRHr__7tEs6vX4VyyBQT+X5ckZ7=w@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1168 bytes --]
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.
Thanks for help,
Pawel
[-- Attachment #1.2: Type: text/html, Size: 1390 bytes --]
[-- Attachment #2: Type: text/plain, Size: 496 bytes --]
___________________________________________________________________________________
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 reply other threads:[~2023-04-18 10:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 10:37 Pawel Urbanski via ntg-context [this message]
2023-04-18 13:29 ` Hans Hagen via ntg-context
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='CADUDiDEovGxyvEgFRH3oFwRHr__7tEs6vX4VyyBQT+X5ckZ7=w@mail.gmail.com' \
--to=ntg-context@ntg.nl \
--cc=urbanski.pawel@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).