From: Michael Saunders <odradek5@gmail.com>
To: ntg-context@ntg.nl
Subject: typescripts
Date: Thu, 18 Mar 2010 15:42:29 -0500 [thread overview]
Message-ID: <54d7f5601003181342nd0ca4ccu8498b0ba35fa027c@mail.gmail.com> (raw)
I'm trying to follow the examples and getting surprising results:
\definefontfeature[default][mode=node,language=dflt,script=latn,kern=yes,liga=yes,tlig=yes,trep=yes]
\definefontfeature[body][default][onum=yes,pnum=yes,protrusion=quality,expansion=quality]
\definefontfeature[smallcaps][body][smcp=yes, onum=yes]
%I understood this to mean that "body" would inherit "default" and
"smallcaps" would inherit "body".
\starttypescript [sans] [gillLT]
\definefontsynonym[Gill-Light][name:gillsansmtprolight][features=body]
\definefontsynonym[Gill-Light-Italic][name:gillsansmtprolightitalic][features=body]
\stoptypescript
\starttypescript [sans] [gillLT]
\definefontsynonym[Sans][Gill-Light][features=body]
\definefontsynonym[SansItalic][Gill-Light-Italic][features=body]
\stoptypescript
\starttypescript [gill]
\definetypeface [gillLT] [ss] [sans] [gillLT] [default]
[features=body,script=latn,script=grek]
\stoptypescript
\setupalign[hanging,hz]
\setupbodyfont[gillLT,12pt]
\ss
1: 1234567890 fi fl ffi ffl \addff{smallcaps} test smallcaps
2: \addff{body} 1234567890 fi fl ffi ffl \addff{smallcaps} test smallcaps
In both 1 & 2, ligatures and small caps fail (though the glyphs are in
the font).
In 1, oldstyle fails.
___________________________________________________________________________________
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-18 20:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 20:42 Michael Saunders [this message]
-- 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 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
2010-03-17 1:26 typescripts Michael Saunders
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
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=54d7f5601003181342nd0ca4ccu8498b0ba35fa027c@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).