From: "George N. White III" <WhiteG@mar.dfo-mpo.gc.ca>
Cc: Giuseppe Bilotta <bourbaki@bigfoot.com>, <ntg-context@ntg.nl>
Subject: Re: More font problems -- CMTT instead of Courier
Date: Fri, 28 Dec 2001 12:35:43 -0400 (AST) [thread overview]
Message-ID: <Pine.GSO.4.43.0112281144540.7580-100000@emerald.bio.dfo.ca> (raw)
In-Reply-To: <5.1.0.14.1.20011227140557.03c78a50@server-1>
On Thu, 27 Dec 2001, Hans Hagen wrote:
> >\starttypescript [sans] [courier] [name]
> >
> >should read
> >
> >\starttypescript [mono] [courier] [name]
>
> Whow, that's indeed a stupid bug.
Well, some of us prefer cmtt over Courier! Some "bugs" really are
features!
Courier exaggerates line break problems with long URL's or embedded source
code (I often use ProTex literate programming to document source code) and
lacks cmtt's "space" character which is useful in situations (e.g.,
Fortran formatted input files) where spaces are significant.
I stopped working with typescripts while trying to get context working
under Win32. Now that I have the 20011201 teTeX beta nearly running in
Cygwin I can start thinking about typescript's again.
Two things I often need are a (fake) caps font and (now) cmtt (e.g.,
instead of Courier). I can enable a caps font generated using fontutil by
redefining a few things right in my files, but I don't seem to be able to
make such tweaks work via a typescript file. The examples in the manuals
show how to add new fonts, but aren't as clear about what is needed when
you only want to make a small change to one of the predefined fonts. Now
that I have two things to tweak it makes more sense to create a new
typescript.
--
George N. White III <gnw3@acm.org> Bedford Institute of Oceanography
next prev parent reply other threads:[~2001-12-28 16:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-25 18:53 Giuseppe Bilotta
2001-12-27 13:06 ` Hans Hagen
2001-12-28 16:35 ` George N. White III [this message]
[not found] ` <Pine.GSO.4.43.0112281144540.7580-100000@emerald.bio.dfo.ca >
2001-12-29 0:42 ` Hans Hagen
2001-12-29 13:07 ` Re[2]: " Giuseppe Bilotta
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=Pine.GSO.4.43.0112281144540.7580-100000@emerald.bio.dfo.ca \
--to=whiteg@mar.dfo-mpo.gc.ca \
--cc=bourbaki@bigfoot.com \
--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).