From: Oliver Mihatsch <oliver.mihatsch@mchp.siemens.de>
Subject: Re: It works
Date: Fri, 15 Mar 2002 17:33:52 +0100 [thread overview]
Message-ID: <200203151633.g2FGXqQO008123@zaire.mchp.siemens.de> (raw)
In-Reply-To: <5.1.0.14.1.20020227004407.02e22f98@server-1>
On Wednesday 27 February 2002 00:53, Hans Hagen wrote:
> At 06:36 PM 2/26/2002 +0100, Frans Goddijn wrote:
> > ...
>
> 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
Is this feature already supposed to work somehow? I tried the following
\starttypescript [serif] [...] [name]
\definefontsynonym [Serif] [...]
\definefontsynonym [SerifBold] [...]
...
\definefontsynonym [OldStyleSerif] [..]
\definefontsynonym [OldStyleSerifBold] [...]
...
\stoptypescript
While experimenting with this, I made the experience that
\def\oldstylenumerals#1{{\getglyph{OldStyle}{#1}}}
does not lead to any oldstyle numbers, whereas
\def\oldstylenumerals#1{{\getglyph{\fontclass OldStyle}{#1}}}
does. The results seem ok. \oldstylenumerals adpts to the font family and
shape. Does this mean that I am on the right track??
Moreover, I discovered a pitfall (bug?). The oldstyle numerals I get this way
have the wrong size, if the typeface has been defined using the
rscale=<number> feature. In other words, my numbers aren't "rscaled."
What is needed to circumvent this?
Oliver
prev parent reply other threads:[~2002-03-15 16:33 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
2002-03-15 16:33 ` Oliver Mihatsch [this message]
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=200203151633.g2FGXqQO008123@zaire.mchp.siemens.de \
--to=oliver.mihatsch@mchp.siemens.de \
/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).