ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Ulrich Dirr" <ud@mucschach.de>
To: "ConTeXt Mailing List" <ntg-context@ntg.nl>
Subject: OpenType beginners question
Date: Mon, 21 Jul 2008 10:05:01 +0200	[thread overview]
Message-ID: <000801c8eb08$79b91ea0$6d2b5be0$@de> (raw)

Hi,

I've adapted the complete luatex/markiv typescript example at
http://wiki.contextgarden.net/Mark_IV#Opentype_features
for FF Kievit Pro I. It works quiet nice out of the box (aaah, nomore
fiddling with font installation!).

\starttypescript [sans] [kievit]

    \definefontsynonym [KievitProRegular]         [name:KievitPro-Regular]
[features=default]
    \definefontsynonym [KievitProMedium]          [name:KievitPro-Medium]
[features=default]
    \definefontsynonym [KievitProExtraBold]       [name:KievitPro-ExtraBold]
[features=default]
 
    \definefontsynonym [KievitProItalic]          [name:KievitPro-Italic]
[features=default]
    \definefontsynonym [KievitProMediumItalic]
[name:KievitPro-MediumItalic]    [features=default]
    \definefontsynonym [KievitProExtraBoldItalic]
[name:KievitPro-ExtraBoldItalic] [features=default]

\stoptypescript

\starttypescript [sans] [kievit]

    \definefontsynonym [Sans]            [KievitProRegular]
[features=default]
    \definefontsynonym [SansItalic]      [KievitProItalic]
[features=default]
    \definefontsynonym [SansBold]        [KievitProMedium]
[features=default]
    \definefontsynonym [SansSlanted]     [SansItalic]
[features=default]
    \definefontsynonym [SansBoldSlanted] [SansBoldItalic]
[features=default]
    \definefontsynonym [SansCaps]        [Sans]
[features=smallcaps]

\stoptypescript

\definetypeface[kievit][rm][sans][kievit][default]
\definetypeface[kievit][ss][sans][kievit][default]
\definetypeface[kievit][tt][mono][modern]  [default][rscale=1.12]
\definetypeface[kievit][mm][math][iwona]   [default][rscale=1.02]

\setupbodyfont[kievit,ss,10pt]

Now \bf \it works perfectly well but \sc doesn't. Do I need some extra
definition?

Best regards,
Ulrich

___________________________________________________________________________________
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
___________________________________________________________________________________


             reply	other threads:[~2008-07-21  8:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-21  8:05 Ulrich Dirr [this message]
2008-07-21  8:38 ` Wolfgang Schuster
2008-07-21  9:37   ` Diego Depaoli
2008-07-21  9:46     ` Andrea Valle
2008-07-27 12:53       ` Taco Hoekwater
2008-07-30 21:53         ` Andrea Valle
2008-07-31  9:58           ` Otared Kavian
2008-07-23  7:19     ` Wolfgang Schuster
2008-07-21 17:17   ` Ulrich Dirr
2008-07-21  9:09 ` Mojca Miklavec
2008-07-21  9:32   ` Thomas A. Schmitz
2008-07-21 16:28   ` Aditya Mahajan

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='000801c8eb08$79b91ea0$6d2b5be0$@de' \
    --to=ud@mucschach.de \
    --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).