From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: simplefonts vs typescripts
Date: Wed, 13 May 2015 18:56:04 +0200 [thread overview]
Message-ID: <55538224.5060604@wxs.nl> (raw)
In-Reply-To: <20150513.120945.29119.0@webmail06.dca.untd.com>
On 5/13/2015 6:09 PM, david.boerschlein@juno.com wrote:
> I am still not able to set up the Noto fonts due mostly to sketchy/lack-of documentation on setting up ConTeXt fonts.
>
> I understand I need to set up typescripts but do not understand the syntax and/or semantics of the different commands and how to map the font names/paths (otf and ttf files) to reference them in the typescripts. I would like to create a utility that will create the typescript file for MKIV from the otf/ttf files themselves.
>
> Please provide me with any help/documentation.
In addition to wolfgangs mail: there is not much science involved in
typescripts, just take another type-imp-*.mkiv file as example ...
type-imp-noto.mkiv :
\starttypescriptcollection[noto]
\starttypescript [serif] [noto] [name]
\setups[font:fallback:serif]
\definefontsynonym
[Serif]
[file:notowhatever.ttf]
[features=default]
\definefontsynonym [SerifBold]
[file:notowhateverbold.ttf]
[features=default]
\definefontsynonym
[SerifItalic]
[file:notowhateveritalic.ttf]
[features=default]
\definefontsynonym
[SerifBoldItalic]
[file:notowhateverbolditalic.ttf]
[features=default]
\stoptypescript
\starttypescript[noto]
\definetypeface [noto] [rm] [serif] [noto] [default]
\definetypeface [noto] [ss] [sans] [dejavu] [default]
\definetypeface [noto] [tt] [mono] [dejavu] [default]
\definetypeface [noto] [mm] [math] [times] [default]
\stoptypescript
\stoptypescriptcollection
\setupbodyfont[noto]
You need to figure out the right filenames yourself (not that hard as
you downloaded them I assume). But simplefonts is less lines of code and
you only need such a typescript if you want to have long term guarantees
(as it depends less on heuristics)
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| 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 / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2015-05-13 16:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 16:09 david.boerschlein
2015-05-13 16:47 ` Wolfgang Schuster
2015-05-13 16:56 ` Hans Hagen [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-05-21 19:40 david.boerschlein
2015-05-21 20:14 ` Pablo Rodriguez
2015-05-21 21:19 ` Wolfgang Schuster
2015-05-04 16:26 david.boerschlein
2015-05-04 16:47 ` Hans Hagen
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=55538224.5060604@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.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).