From: Willi Egger <w.egger@boede.nl>
To: NTG-Context ConTeXt users <ntg-context@ntg.nl>
Subject: Using fontfeatures ...
Date: Wed, 16 Jul 2008 14:48:23 +0200 [thread overview]
Message-ID: <1BBEED62-9197-4331-A1BB-6CA8E1828AD3@boede.nl> (raw)
Hi,
I am trying to use fontfeatures contained in my new otf-font Seravek.
I am getting Seravek in the file but no way to activate the oldstyle
figures and the small caps. :-(
Can someone give m a clue?
Willi
I got until now the following typescript:
% \definefontfeature
% [OldstyleFigures]
%
[language=nld,script=latn,mode=node,calt=no,clig=yes,rlig=yes,onum=yes]
\starttypescript [sans] [seravek]
\definefontsynonym [SeravekBasic-Roman] [file:SeravekBasic-
Regular] [features=default]
\definefontsynonym [SeravekBasic-Bold] [file:SeravekBasic-
Bold] [features=default]
\definefontsynonym [SeravekBasic-Italic] [file:SeravekBasic-
RegularItalic][features=default]
\definefontsynonym [SeravekBasic-Bold-Italic][file:SeravekBasic-
BoldItalic] [features=default]
\stoptypescript
\starttypescript [sans] [seravek] [name]
\definefontsynonym [Sans] [SeravekBasic-Roman]
[features=default]
\definefontsynonym [SansItalic] [SeravekBasic-Italic]
[features=default]
\definefontsynonym [SansBold] [SeravekBasic-Bold]
[features=default]
\definefontsynonym [SansBoldItalic] [SeravekBasic-Bold-Italic]
[features=default]
\definefontsynonym [SansRegularCaps] [Sans]
[features=smallcaps]
% \definefontsynonym [SansBoldCaps]
[SansBold] [features=smallcaps]
% \definefontsynonym [SansItalicCaps]
[SansItalic] [features=smallcaps]
% \definefontsynonym [SansBoldItalicCaps]
[SansBoldItalic] [features=smallcaps]
\stoptypescript
\starttypescript [Seravek]
\definetypeface [Seravek] [ss] [sans][seravek][default]
\definetypeface [Seravek] [mm] [math] [modern][default]
\stoptypescript
I tried this with the following test-code:
\setupoutput[pdftex]
\enableregime[utf]
% \definefontfeature
% [OldstyleFigures]
%
[language=nld,script=latn,mode=node,calt=no,clig=yes,rlig=yes,onum=yes]
\definefontfeature[default]
[method=node,script=latn,language=dflt,liga=yes,onum=yes,kern=yes]
\usetypescriptfile[seravek]
\usetypescript[Seravek]
\setupbodyfont[Seravek,12pt]
% \def\sc{\setfontfeature{smcp}}
% \def\os{\setfontfeature{onum}}
\starttext
Hello World! {\sc ABC abc} {\os 123} 1 2 3 4 5 6 7 8 9
\blank
{\sc Hello World!}
\blank
{\bf Hello World! {\sc ABC abc} {\os 123} 1 2 3 4 5 6 7 8 9}
\blank
{\it Hello World! {\sc ABC abc} {\os 123} 1 2 3 4 5 6 7 8 9}
\blank
\bi Hello World {\sc ABC abc} {\os 123} 1 2 3 4 5 6 7 8 9!
\stoptext
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2008-07-16 12:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 12:48 Willi Egger [this message]
2008-07-16 12:56 ` Wolfgang Schuster
2008-07-16 13:29 ` Willi Egger
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=1BBEED62-9197-4331-A1BB-6CA8E1828AD3@boede.nl \
--to=w.egger@boede.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).