ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Adam Lindsay" <atl@comp.lancs.ac.uk>
Subject: Re: Will the real palatino please stand up?
Date: Fri, 22 Apr 2005 16:40:04 +0100	[thread overview]
Message-ID: <20050422164004.14366@mail.comp.lancs.ac.uk> (raw)
In-Reply-To: <200504221049.09828.john@wexfordpress.com>

John R. Culleton said this at Fri, 22 Apr 2005 10:49:09 +0000:

>In the typescript file type-syn.tex the palatino font is defined
>four times, twice for math and twice for serif.  The headers in
>each pair are identical, e.g.:
>
>\starttypescript [serif] [palatino] [name]
>
>
>Assume I want to use the second serif typescript, the one that uses
>the Palladio fonts. Using the \usetypescript statement, how do I
>specify that particular script? 

They all get loaded.
The second group (corresponding with the second [serif] [palatino]
[ec,texnansi,8r] typescript in type-enc) is a set of bonus extras, not
stand-alone, that help call in the FPLv1 fonts, which are:
Regular Caps & OsF,
Italic OsF,
Bold OsF, and
BoldItalic OsF.

The different glyph shapes mean they can't really be used on their own as
a family, but rather called out as variants, generally for Old Style
Figures. Actually, the "bonus definitions" down at the bottom of type-syn
are preparation for font variants. So after installing the FPL[1] fonts,
adding the following to your environment:

\definefontvariant [Serif] [os] [OsF]

...allows you to get oldstyle figures with markup like {\Var[os]123}.

However (and I can already hear the question forming on some people's
lips), if you want pervasive OsFs in your Palatino document, without
having to mark each numeric string, you're better off installing the FPL-
Neu fonts[2], using an old-stylish encoding like one listed in Idris's
recent MyWay or in the distro[3].

[1]<http://www.ctan.org/tex-archive/fonts/fpl/>
[2]<http://home.vr-web.de/was/x/FPL/>
[3] fonts/enc/dvips/context/texnansi-os-lm.enc

Cheers,
adam
-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Adam T. Lindsay, Computing Dept.     atl@comp.lancs.ac.uk
 Lancaster University, InfoLab21        +44(0)1524/510.514
 Lancaster, LA1 4WA, UK             Fax:+44(0)1524/510.492
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2005-04-22 15:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-22 10:49 John R. Culleton
2005-04-22 15:40 ` Adam Lindsay [this message]
2005-04-22 15:47   ` Adam Lindsay

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=20050422164004.14366@mail.comp.lancs.ac.uk \
    --to=atl@comp.lancs.ac.uk \
    --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).