From: Hans Hagen <pragma@wxs.nl>
Subject: Re: fontvariants
Date: Sun, 04 Dec 2005 21:52:28 +0100 [thread overview]
Message-ID: <4393570C.30602@wxs.nl> (raw)
In-Reply-To: <4391C9B1.4010002@comp.lancs.ac.uk>
Adam Lindsay wrote:
> Hans van der Meer wrote:
>
>> I was probing into the font variant mechanism.
>>
>> QUESTION: Is the variant mechanism exclusively tied to the series
>> Serif (\rm) and Sans (\ss)?
>
>
> Yes, pretty much, in the implementation's design.
more precisely, it;s related to rm|ss|tt (mapped onto Serif Sans Mono)
Hans
prev parent reply other threads:[~2005-12-04 20:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-03 12:33 fontvariants Hans van der Meer
2005-12-03 16:37 ` fontvariants Adam Lindsay
2005-12-04 20:52 ` Hans Hagen [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=4393570C.30602@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).