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] Non-standard font alternatives
Date: Wed, 19 Apr 2023 16:53:23 +0200 [thread overview]
Message-ID: <CADUDiDHpfR1qmypkLMxEMSMpDmNYix15d=gq70AP4zyzSN1edg@mail.gmail.com> (raw)
In-Reply-To: <673a7766-5218-dba5-7dac-a8922fa0718f@freedom.nl>
[-- Attachment #1.1: Type: text/plain, Size: 961 bytes --]
>
> Dear Matthew,
I wrote you off the list in connection to the other thread where Hans
helped me with using Roboto Flex.
I used your typescript definitions but the font is not embedded in the
document.
** I've copied all the ttf font files to the recommended directory
structure under: texmf-local/fonts/truetype.
** I've created a type-imp-roboto.mkiv file and saved it in the recommended
location under: texmf-local/tex/.../mkiv/.
Using: \usetypescript or \usetypescriptfile or \usebodyfont [roboto] with
setuphead does not work.
I use the following simplest setup command:
\setuphead[chapter][style={\switchtobodyfont[roboto,20pt]\ss}]
I will be glad to join forces and create the typescript file but maybe
missing something obvious. While I could use an inline definition suggested
by Hans in the other thread, Roboto is a great font and I or other people
would like to use it as a shared resource.
All the best and thanks for help and feedback,
Pawel
[-- Attachment #1.2: Type: text/html, Size: 1592 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 prev parent reply other threads:[~2023-04-19 14:54 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
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 ` Pawel Urbanski via ntg-context [this message]
2023-04-19 16:52 ` [NTG-context] " 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='CADUDiDHpfR1qmypkLMxEMSMpDmNYix15d=gq70AP4zyzSN1edg@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).