From: Hans Hagen <pragma@wxs.nl>
Cc: "NTG-ConTeXt mailing list" <ntg-context@ntg.nl>
Subject: Re: It works
Date: Wed, 27 Feb 2002 00:53:00 +0100 [thread overview]
Message-ID: <5.1.0.14.1.20020227004407.02e22f98@server-1> (raw)
In-Reply-To: <008501c1beec$1c8f57c0$6401a8c0@lap>
At 06:36 PM 2/26/2002 +0100, Frans Goddijn wrote:
>knows what might happen if the font setup gets upgraded again...) I provide
one reason for introducing typescripts was that i wanted as less files as
possibl eand the old way would lead to many many files (as well as
potential conflicts in names); so consider typescripts kind of stable
given that you have:
\definefontsynonym [Times-RomanSC] [tnrexp]
you can now say:
>\definefont[Oldstyle][tnrexp]
\definefont[OldStyle][Times-RomanSC]
[you can also decide to put this within the typescipt itself
>\def\oldstylenumerals#1{{\Oldstyle #1}}
>\def\os#1{{\Oldstyle #1}}
>
>\definefont[OldstyleItalic][tnrexpi]
>\def\oldstyleitnumerals#1{{\OldstyleItalic #1}}
>\def\osi#1{{\OldstyleItalic #1}}
>
>%\let\os\Oldstyle
>%\let\osi\OldstyleItalic
Remind me that i provide you a better solution for this, something:
\definefontsynonym [OldStyleSerif] [....]
\definefontsynonym [OldStyleSerifItalic] [....]
\define....
\def\oldstylenumerals#1{{\getglyph{OldStyle}{#1}}}
will give you a cleaner interface to this as well automatically adapt
itself to the styles.
Some day i will buy a couple of those fonts and give them a try
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
fall-back web server:
www.pragma-pod.nl
-------------------------------------------------------------------------
next prev parent reply other threads:[~2002-02-26 23:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 17:36 Frans Goddijn
2002-02-26 23:53 ` Hans Hagen [this message]
2002-03-15 16:33 ` Oliver Mihatsch
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=5.1.0.14.1.20020227004407.02e22f98@server-1 \
--to=pragma@wxs.nl \
--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).