From: "Adam Lindsay" <atl@comp.lancs.ac.uk>
Subject: font variants
Date: Fri, 19 Nov 2004 14:11:39 +0000 [thread overview]
Message-ID: <20041119141139.19722@news.comp.lancs.ac.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 2220 bytes --]
Hi all,
I just wanted to run this technique by you all, and get a bit of
feedback, both on the utility as well as the style of the solution.
I'm a bit unhealthily obsessed by fonts, especially with getting the most
out of the various features. Unfortunately, each vendor expresses
different features in different ways, so that leads to font-sensitive
markup. This problem explodes in the OpenType and XeTeX world, because of
the number of features each font exposes.
However, it's relevant in the pdfTeX/type1 world as well. Just last
night, I discovered the FPL fonts (SC/OsF for URW Palladio) on CTAN
(<http://www.ctan.org/tex-archive/fonts/fpl/>). How does one access the
old style figures in this font without knowing intimately about the font?
I took inspiration (and code) from the Unicode font mechanisms and the
new font effects. The code is in the attached test-psc, the typescript in
type-psc. The result is at <http://homepage.mac.com/atl/tex/test-psc.pdf>.
What this does and doesn't do:
- generalises font access to features in associated fonts
- adapts itself to current size/family/alternative
- doesn't allow further adaptation (e.g., \it \Var[osf] 123 \bf 456)
- best for short runs of associated fonts (e.g., OsF, sub/superscripts)
- can insert arbitrary features into existing typescripts
- relies on a couple special naming conventions within typescripts
- can be defined based on Serif/Sans/Mono family
- is not currently defined based on bodyfont namespace.
Is this more desirable with people \switchbodyfont ing in a doc?
- allows expansion beyond \tf\bf\it\bi\sl\bs\sc choices.
Any thoughts?
(If anyone wants to give pointers on the correct usage/relevance of
[#1][#2]#3 parameters, pushfont/popfont, and adapting to bodyfont
namespaces, please feel free!)
[Hans, if you see the general utility of this kind of solution, I'd
appreciate the addition of Caps to the \fontstylesuffix.]
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
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
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2.1: test-psc.tex --]
[-- Type: application/x-tex, Size: 1398 bytes --]
[-- Attachment #2.2: type-psc.tex --]
[-- Type: application/x-tex, Size: 991 bytes --]
[-- Attachment #3: Type: text/plain, Size: 139 bytes --]
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
next reply other threads:[~2004-11-19 14:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 14:11 Adam Lindsay [this message]
2004-11-19 15:11 ` Hans Hagen
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=20041119141139.19722@news.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).