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: Re: [NTG-context] Google's Roboto Flex font typescript and goodies definition.
Date: Wed, 19 Apr 2023 16:06:14 +0200 [thread overview]
Message-ID: <be3a3139-5f77-56b9-6d23-0c792c0317bb@gmail.com> (raw)
In-Reply-To: <7cab8e88-c9ca-7170-8d94-d9ed648f8c13@freedom.nl>
Dear Hans,
Thank you for the template. Roboto Flex gets embedded in the generated
PDF document.
I read the co-fonts manual and the wiki once again. I'll try to put
together a handful of ideas for rewriting the wiki to make certain
concepts more friendly for beginners.
My next step will be to create a proper working
type-imp-roboto-flex.mkiv and type-imp-roboto.mkiv for the non-variable
font edtion to be more portable. Roboto is a very good font and is
recommended as a body font for presentations or headings, which made me
use in the first place.
I must admit that I am struggling a bit but will try to take small steps
when creating that typescrip definition file.
All the best and thank you,
Pawel
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2023-04-19 14:06 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
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 [this message]
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=be3a3139-5f77-56b9-6d23-0c792c0317bb@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).