From: Steffen Wolfrum <context@st.estfiles.de>
Cc: Adam Lindsay <atl@comp.lancs.ac.uk>
Subject: OpenType and XeConTeXt
Date: Tue, 14 Feb 2006 11:22:21 +0100 [thread overview]
Message-ID: <93E6CE25-2D58-428C-A212-6114A4BEEE51@st.estfiles.de> (raw)
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?
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?
Thank you,
Steffen
next reply other threads:[~2006-02-14 10:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 10:22 Steffen Wolfrum [this message]
2006-02-14 12:46 ` Adam Lindsay
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=93E6CE25-2D58-428C-A212-6114A4BEEE51@st.estfiles.de \
--to=context@st.estfiles.de \
--cc=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).