From: Michael Saunders <odradek5@gmail.com>
To: ntg-context@ntg.nl
Subject: typescripts
Date: Tue, 16 Mar 2010 20:26:23 -0500 [thread overview]
Message-ID: <54d7f5601003161826n452408ahb6ae611b2fa078cf@mail.gmail.com> (raw)
I have been earnestly trying to understand how they work by attempting
a slightly more complex one.
So far, I have:
-------------------------------------------------------
\definefontfeature[default][mode=node,language=dflt,script=latn,kern=yes,liga=yes,tlig=yes,trep=yes]
\definefontfeature[body][onum=yes,pnum=yes,protrusion=quality,expansion=quality]%turn
hz on
%plus some I hope to use later
\definefontfeature[tabular][sans=yes,tnum=yes,onum=yes]%turn hz off
\definefontfeature[allcaps][cpsp=yes,case=yes,lnum=yes]
\definefontfeature[smallcaps][smcp, onum=yes]
\definefontfeature[swashes][swsh=yes]
\definefontfeature[inferior][sinf=yes]
\definefontfeature[superior][sups, ordn=yes]
\definefontfeature[numerator][numr=yes]
\definefontfeature[denominator][dnom=yes]
\definefontfeature[prop-os][pnum=yes,onum=yes]
\definefontfeature[prop-lin][pnum=yes,lnum=yes]
\definefontfeature[tab-os][tnum=yes,onum=yes]
\definefontfeature[tab-lin][tnum=yes,lnum=yes]
\definefontfeature[ornaments][ornm=yes]
\definefontfeature[lgc][script=latn,script=grek,script=cyrl]
\starttypescript [serif] [junicode]
\definefontsynonym[Junicode][name:junicode][features=default,features=body,features=lgc]
\definefontsynonym[Junicode-Bold][name:junicodebold][features=default,features=body,features=lgc]
\definefontsynonym[Junicode-Italic][name:junicodeitalic][features=default,features=body,features=lgc]
\definefontsynonym[Junicode-BoldItalic][name:junicodebolditalic][features=default,features=body,features=lgc]
\stoptypescript
\starttypescript [serif] [junicode]
\definefontsynonym[Serif][Junicode][features=default,features=body,features=lgc]
\definefontsynonym[SerifBold][Junicode-Bold][features=default,features=body,features=lgc]
\definefontsynonym[SerifItalic][Junicode-Italic][features=default,features=body,features=lgc]
\definefontsynonym[SerifBoldItalic][Junicode-BoldItalic][features=default,features=body,features=lgc]
\stoptypescript
\starttypescript [junicode]
\definetypeface [junicode] [rm] [serif] [junicode] [default]
[features=default,features=body,features=lgc,features=hanging,features=hz]
\stoptypescript
\setupalign[hanging,hz]
\setupbodyfont[junicode,12pt]
-------------------------------------------------------------------------
but,
1. tlig and trep aren't working, so evidently, features=default isn't
getting through. No hanging or hz is happening either---probably the
same problem.
2. As far as I can tell from trying to decode examples, there is some
hidden connection between the first arguments of the second typescript
block and the font switches. So, for example, a secret connection
between SerifBoldItalic and \bi seems to connect Junicode-BoldItalic
to \bi. Fine, but, in all the examples I've seen, there are no more
than two weights and no widths. In some cases, I have five weights
(light, book, medium, semi-bold, bold). How do I set up the
typescript for this and the switches in the text? Must I learn more
pairs like (SerifBoldItalic, \bi)?
___________________________________________________________________________________
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 reply other threads:[~2010-03-17 1:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 1:26 Michael Saunders [this message]
2010-03-17 8:20 ` typescripts Wolfgang Schuster
2010-03-17 9:04 ` typescripts Mojca Miklavec
2010-03-17 9:11 ` typescripts Wolfgang Schuster
2010-03-17 11:33 ` typescripts Mojca Miklavec
2010-03-17 12:12 ` typescripts Wolfgang Schuster
-- strict thread matches above, loose matches on Subject: below --
2010-11-12 14:32 typescripts Herbert Voss
2010-11-12 16:29 ` typescripts Herbert Voss
2010-11-12 16:54 ` typescripts Hans Hagen
2010-11-12 16:57 ` typescripts Hans Hagen
2010-11-12 17:41 ` typescripts Herbert Voss
2010-11-12 17:46 ` typescripts Hans Hagen
[not found] ` <4CDD80A7.7040803@FU-Berlin.DE>
[not found] ` <4CDD8246.2020206@wxs.nl>
2010-11-12 20:39 ` typescripts Herbert Voss
2010-11-10 18:57 typescripts Herbert Voss
2010-11-10 20:28 ` typescripts Mojca Miklavec
2010-11-10 21:14 ` typescripts Herbert Voss
2010-11-11 5:20 ` typescripts Wolfgang Schuster
2010-11-11 11:03 ` typescripts Mojca Miklavec
2010-11-11 11:27 ` typescripts Hans Hagen
2010-11-11 14:15 ` typescripts Mojca Miklavec
2010-03-18 20:42 typescripts Michael Saunders
2010-03-18 1:32 typescripts Michael Saunders
2010-03-18 9:53 ` typescripts Wolfgang Schuster
2010-03-18 10:04 ` typescripts Wolfgang Schuster
2010-03-17 12:16 typescripts Michael Saunders
2010-03-17 12:34 ` typescripts Wolfgang Schuster
2010-03-18 0:04 ` typescripts Wolfgang Schuster
2003-08-16 20:05 typescripts Henning Hraban Ramm
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=54d7f5601003161826n452408ahb6ae611b2fa078cf@mail.gmail.com \
--to=odradek5@gmail.com \
--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).