ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: More font problems -- CMTT instead of Courier
Date: Sat, 29 Dec 2001 01:42:53 +0100	[thread overview]
Message-ID: <5.1.0.14.1.20011229013740.031da368@server-1> (raw)
In-Reply-To: <Pine.GSO.4.43.0112281144540.7580-100000@emerald.bio.dfo.ca >

At 12:35 PM 12/28/2001 -0400, you wrote:
>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

right! the variable width font cmvtt10 is also pretty good.

btw, it is no problem to combine serif/sans/mono typescripts, but beware of 
relative scaling; this is why the scale factor is sometimes set in a 
typeface definition

>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.

in many cases you only need to remap a filename

i think that it's worth looking into the caps and use cap fonts instead of 
scaled ones; it's more robust to have caps in the lowercase slots than to 
uppercase a string.

Hans
-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------


  parent reply	other threads:[~2001-12-29  0:42 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
     [not found]   ` <Pine.GSO.4.43.0112281144540.7580-100000@emerald.bio.dfo.ca >
2001-12-29  0:42     ` Hans Hagen [this message]
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=5.1.0.14.1.20011229013740.031da368@server-1 \
    --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).