From: Hans Hagen <pragma@wxs.nl>
Subject: Re: low level fonts
Date: Thu, 25 Nov 2004 13:11:49 +0100 [thread overview]
Message-ID: <41A5CC05.7050005@wxs.nl> (raw)
In-Reply-To: <20041125104109.18456@news.comp.lancs.ac.uk>
Adam Lindsay wrote:
> hi all.
>
> what's your best way of getting the current font name, regardless of how
> it's set (e.g., typescript, unicode, definedfont, low-level \font
> definitions...)?
>
> I certainly know about \truefontname{}, but what to put in the braces?
tex: \fontname\font
also in context: \purefontname\font
\font\myfont AdamBold at 123pt
\fontname \myfont -> AdamBold at 123pt
\purefontname\myfont -> AdamBold
so,
\definefont[Whatever][\purefontname{\font} at 24.56pt]
is probably what you're looking for
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~2004-11-25 12:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-25 10:41 Adam Lindsay
2004-11-25 12:11 ` Hans Hagen [this message]
2004-11-25 13:48 ` Adam Lindsay
2004-11-25 15:09 ` Adam Lindsay
2004-11-25 16:28 ` 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=41A5CC05.7050005@wxs.nl \
--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).