From: ecashin@coe.uga.edu (Ed L. Cashin)
Subject: the world of fonts ([David Carlisle] Re: questions)
Date: 06 Oct 1999 14:18:33 -0400 [thread overview]
Message-ID: <m3670kbbeu.fsf@kali.coe.uga.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 44 bytes --]
I saw this post in the pdftex mailing list:
[-- Attachment #2: Type: message/rfc822, Size: 1487 bytes --]
From: David Carlisle <davidc@nag.co.uk>
To: mikes@athabascau.ca
Cc: oberdiek@ruf.uni-freiburg.de, pdftex@tug.org
Subject: Re: questions
Date: Mon, 4 Oct 1999 14:35:11 +0100 (BST)
Message-ID: <199910041335.OAA21656@nag.co.uk>
> The problem, I think, would be having to make sure
> the new quotes match up in that many documents.
In that case use T1 encoding and get straight quotes.
since this is the pdftex list, beware that the default T1 encoded
computer modern fonts are ec fonts which are not freely available in
type1 form. You can use the ae package to get round this or use a font
set other than computer modern, eg \usepackage{times}
David
[-- Attachment #3: Type: text/plain, Size: 905 bytes --]
It reminds me of a situation I'm now in. There is a document that
uses metapost to typeset text on top of another metapost image (using
plain tex--I did this project before I started using context). I'm
using the cmtt10 font so that I can count on some relation between the
length of the text and the space it will require, and I'm handling
line-breaking manually (with perl).
Now the users would like a bolder font. I don't see a cmttbx10 or
anything. I know that there is much more to fonts than I now know. I
hear people talking about virtual fonts and all kinds of stuff. Maybe
I could get a bolder teletype font by learning more about fonts in
general.
How could I learn about ways to use other (preferably free) fonts with
TeX in such a way that I'll also be able to apply this new learning to
context, which I'm moving toward more and more?
--
--Ed Cashin
ecashin@coe.uga.edu
reply other threads:[~1999-10-06 18:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m3670kbbeu.fsf@kali.coe.uga.edu \
--to=ecashin@coe.uga.edu \
/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).