ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Re: URw metric files
Date: Thu, 22 Dec 2005 23:55:53 +0100	[thread overview]
Message-ID: <43AB2EF9.5080708@elvenkind.com> (raw)
In-Reply-To: <43AB24CD.6020909@wxs.nl>


Hi,


Hans Hagen wrote:
>> My last one, yes. The one that only has lm->cm synonyms, nothing else.
> 
> how about vietnamese ... we need to move the berry names to akb then:

I see now that there are no vietnamese fonts in cont-fnt.zip,
I thought you had included the t5 metrics as well.
Those fonts should not be deleted from type-dis then, sorry.

> [berry] vs. [adobekb]
> does this makes sense?

My original take was: if you know how to install the next context
release, then you also know how to install cont-fnt, and no other
trickery would be needed to get these postscript fonts to work.
Just install cont-fnt if you want texfont names, or use e.g.

   \usetypescript[adobekb][ec]
   \usetypescript[palatino][ec]

if you want to stick to berry names. Anything else will give
you a "missing font" error, but one that should be easier to
solve than the current "utmr8y" errors.

So my plan was: no additional changes, just some removed
\fontsynonyms: the ones that map to (regularly) unavailable fonts.

> (The u* and p* files do differ, don't they? If so, what are the 
> compatibility issues involved? I remember some differences in spacing.)

I do not think there will be compatibility issues since the old
type-dis used the same actual metrics as the texfont-installed ones
(both the u* (fontinst) and the [encoding]-u* (texfont) ones are
based on the same .afm files, by URW).

The only different ones are the p* ones that are (already and still
will be) loaded by \usetypescript[adobekb]. These may or may not
be based on actual Adobe metrics, I am not sure.

Cheers,
Taco

      reply	other threads:[~2005-12-22 22:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-21 16:21 How to setup this type of header? R S Ananda Murthy
2005-12-21 17:56 ` Taco Hoekwater
2005-12-21 19:44   ` David Arnold
2005-12-21 20:13     ` Gerben Wierda
2005-12-22  9:32       ` Hans Hagen
2005-12-21 20:32     ` URw metric files (was: Re: How to setup this type of header?) Taco Hoekwater
2005-12-22 11:18       ` URw metric files Hans Hagen
2005-12-22 11:21       ` Hans Hagen
2005-12-22 12:15         ` Taco Hoekwater
2005-12-22 14:53           ` Hans Hagen
2005-12-22 15:23             ` Taco Hoekwater
2005-12-22 21:07               ` Hans Hagen
2005-12-22 22:12           ` Hans Hagen
2005-12-22 22:55             ` Taco Hoekwater [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=43AB2EF9.5080708@elvenkind.com \
    --to=taco@elvenkind.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).