From: "Adam Lindsay" <atl@comp.lancs.ac.uk>
Subject: Re: texfont and font mechanism
Date: Tue, 19 Aug 2003 00:29:27 +0100 [thread overview]
Message-ID: <20030818232927.30395@smtp.btinternet.com> (raw)
In-Reply-To: <FD271E06-D1BD-11D7-BD36-0030659899AA@fiee.net>
Henning Hraban Ramm said this at Mon, 18 Aug 2003 22:53:15 +0200:
>> define a font family for roman caps [rc] beside the roman [rm] font
>> family. A change to small caps is done with \switchstyleonly[rc], so if
>> you're in SerifBold, you end up in SerifCapsBold.
>
>Good idea.
>I don't really understand the family mechanism.
>Can I define all "styles" like rm, ss... or is
>ist limited (other than the lack of free two-
>letter-combinations)?
I have suggested [rc] (roman caps) and [cs] (caps sans) to complement rm
and ss. I see no reason why it couldn't go further. Things like [hw]
might need some foundational/fallback definitions, though. Need to look
further.
>> It ends up being memory-hungry, and probably a bit slower than other
>> options, but it kinda works.
>
>I like high level solutions, so I need always
>lots of memory... ;-)
Yeah. Me too.
>> Funny coincidence, I was looking around apostrophic labs and other free
>> fonts as well, this weekend. Then I found fontsanon.com. :)
>
>And what do you think? Better? (I'll have a look later.)
>I spent some hours writing (that is, ordering and editing)
>typescripts for Meade's Street family.
>Don't know if I'll use it...
Hey, that's pretty nifty. I installed loads of fonts, but have nothing in
the way of typescripts. I also liked Florencesans and your insight of
putting reverse-italics (yuck) in the slanted slot. And this is *after* I
spent the weekend compulsively texfonting every default Mac font I could
find on my machine.
Did anyone get Scriptina to install? The pltotf step in texfont still hangs.
Cheers,
adam
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Adam T. Lindsay atl@comp.lancs.ac.uk
Computing Dept, Lancaster University +44(0)1524/594.537
Lancaster, LA1 4YR, UK Fax:+44(0)1524/593.608
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2003-08-18 23:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-17 13:18 Henning Hraban Ramm
2003-08-17 15:25 ` John Culleton
2003-08-18 8:22 ` Hans Hagen
2003-08-18 20:44 ` Henning Hraban Ramm
2003-08-17 21:58 ` Adam Lindsay
2003-08-18 20:53 ` Henning Hraban Ramm
2003-08-18 23:29 ` Adam Lindsay [this message]
2003-08-19 14:45 ` Jens-Uwe Morawski
2003-08-19 14:47 ` Adam Lindsay
2003-08-19 17:34 ` Jens-Uwe Morawski
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=20030818232927.30395@smtp.btinternet.com \
--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).