ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Peter Sojan <ilikeunix@gmx.net>
Subject: Small-Caps and Old-Style numbers
Date: Thu, 19 Sep 2002 13:21:05 +0200	[thread overview]
Message-ID: <20020919112104.GA14492@zargon-client1.chello.at> (raw)

Hi!

I took my Adobe Garamond font package from LaTeX (with all the 
virtual fonts defined etc.) and adapted it to work with Context 
(by inspecting the LaTeX .fd files):

-----------------------------------------------------------------
\usetypescriptfile[type-buy]

\starttypescript [serif] [garamond] [ec]
  \definefontsynonym [Garamond-Roman]       [padr9e]  [encoding=ec]
  \definefontsynonym [Garamond-Bold]        [padb9e]  [encoding=ec]
  \definefontsynonym [Garamond-Italic]      [padri9e] [encoding=ec]
  \definefontsynonym [Garamond-Bold-Italic] [padbi9e] [encoding=ec]
  \definefontsynonym [Garamond-Caps]        [padrc9e] [encoding=ec]
  \definefontsynonym [Garamond-Bold-Caps]   [padbc9e] [encoding=ec]
\stoptypescript

\starttypescript [serif] [garamond] [name]
  \usetypescript[serif][fallback]
  \definefontsynonym [Serif]           [Garamond-Roman]
  \definefontsynonym [SerifBold]       [Garamond-Bold]
  \definefontsynonym [SerifItalic]     [Garamond-Italic]
  \definefontsynonym [SerifBoldItalic] [Garamond-Bold-Italic]
  \definefontsynonym [SerifCaps]       [Garamond-Caps]
  \definefontsynonym [SerifBoldCaps]   [Garamond-Bold-Caps]
\stoptypescript

\starttypescript [Garamond] 
  \definetypeface [MyGaramond] [rm] [serif] [garamond] [default] [encoding=ec]
\stoptypescript
-----------------------------------------------------------------

Everything works fine! Two questions left: 

1. Bold-Caps, how do I access them? Is something like 
   "SerifBoldCaps" allowed?

2. How should I integrate Old-Style numbers, so that a switch with 
   \os works? Under Latex the solution from the packager was to 
   reimplement all fonts with a different filename. That is 
   instead of padr9e, padr9d would be used for Garamond-Roman with 
   Old-Style numbers. Obviously this (virtual) font maps-in old 
   style number-glyphs from the adobe extension font and keeps 
   everything else as is. 

   One solution would be to setup another typescript with old-style 
   fonts and switch to it everytime directly by \usetypescript and 
   \switchtobodyfont. But using "\os" would just be nicer.   

Thx, 
Peter


             reply	other threads:[~2002-09-19 11:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-19 11:21 Peter Sojan [this message]
2002-09-19 12:08 ` Bill McClain
2002-09-19 22:16   ` Peter Sojan
2002-09-19 19:27 Bruce D'Arcus
2002-09-19 19:51 ` Bill McClain

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=20020919112104.GA14492@zargon-client1.chello.at \
    --to=ilikeunix@gmx.net \
    /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).