From: Adam Lindsay <atl@comp.lancs.ac.uk>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: OpenType and XeConTeXt
Date: Tue, 14 Feb 2006 12:46:05 +0000 [thread overview]
Message-ID: <43F1D10D.4040600@comp.lancs.ac.uk> (raw)
In-Reply-To: <93E6CE25-2D58-428C-A212-6114A4BEEE51@st.estfiles.de>
Steffen Wolfrum wrote:
> Hi,
>
> using ConTeXt with XeTeX seems to be an nice option for us MacOSX users.
> But I get always confused with the names for these rich features like
> Style Option, Ligatures, Variants.
>
> I mean: how do I know how many variants and style options a font has and
> how they and their ligatures etc. want to be called?
> In plain ConTeXt (for the 255 characters) we can use \showfont[...] and
> \showcharacters in order to know how to call the specific
> characters/glyphs. But what about OpenType?
\showfont is limited to unicode's 0-255 slots, but it's functional:
\showfont["Book Antiqua"]
> Peeking at the LaTeX side of XeTeX, I saw that they have created a
> packages called fontspec which seems to give better access to all (?) if
> these options.
>
> What about us? Is there help also for XeConTeXt?
I find that the lcdf typetools are a tremendous help:
> otfinfo -f ~/Library/Fonts/WarnockPro-Regular.otf
aalt Access All Alternates
c2sc Small Capitals From Capitals
case Case-Sensitive Forms
cpsp Capital Spacing
cswh Contextual Swash
dlig Discretionary Ligatures
dnom Denominators
fina Terminal Forms
frac Fractions
hist Historical Forms
kern Kerning
liga Standard Ligatures
lnum Lining Figures
numr Numerators
onum Oldstyle Figures
ordn Ordinals
ornm Ornaments
pnum Proportional Figures
salt Stylistic Alternates
sinf Scientific Inferiors
size Optical Size
smcp Small Capitals
sups Superscript
tnum Tabular Figures
zero Slashed Zero
and I can test the features with:
\showfont["Warnock Pro: +smcp"]
Fontspec is an impressive piece of work, but I think it's driven much
more by the 'possible' than by requirements. My time constraints (i.e.,
daughter) won't let me do that sort of exploratory coding anymore. I can
try and help out with concrete requests, though.
[I feel like a lot of the stuff I've done in this space has been
released into a vacuum, and that few people are actually making stuff
with OpenType and/or XeConTeXt.]
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
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2006-02-14 12:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 10:22 Steffen Wolfrum
2006-02-14 12:46 ` Adam Lindsay [this message]
2006-02-15 11:52 ` Charles Doherty
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=43F1D10D.4040600@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).