From: h h extern <pragma@wxs.nl>
Subject: Re: How to cook Garamond
Date: Sun, 03 Apr 2005 22:07:29 +0200 [thread overview]
Message-ID: <42504D01.3070207@wxs.nl> (raw)
In-Reply-To: <42AC552A@webmail.colostate.edu>
Idris Samawi Hamid wrote:
> Dear syndicate,
ok, the always messy font business ...
the problem is not so much in context since what it needs is just a bunch of
files, but in the simple fact that there are conflicting demands/messy situations
- we need to be able to install commercial fonts (no metrics available)
- some fonts come in more versions (different vendors)
- some users need something different that default/ec/texnansi
- many users want to use metrics from the distributions
- but as times goes by, distributions change, font are renamed, come and go
- the way pdftex deals with fonts improves over time, for instance nowadays one
can load map files on any page
- some users load map files on demand, others use the big one and therefore
depend on the [not portable] platform tools like updmap
- locations in the texmf tree change (texmf, texmf-dist, enc/map paths) and
although it is possible to catch a lot [downward compatibility] with the
texmf.cnf file this is not what happens in practice
- also, part of the problem is that the past still rules (design sizes, math
versus text, normal glyphs versus composed ones)
the problem can partically be solved by
- providing more typescripts (i add entries to type-buy, type-fsf, type-ghz for
each commercial font i use)
- distributing metrics for commercial fonts (+ type-win)
- try to avoid conflicting demands (using platform font names for not
distributed fonts)
the same is true for hyphenation patterns, and i already have put context
friendly version on the web; i will probably add them to the distribution
also, if you use context exclusively or don't have a problem with some
redundancy, live is more comfortable too.
currently when things go wrong there are two situations:
- no metrics found (tex error)
- no enc/map/pfb/ttf found (pdftex backend problem)
when sorting out things, try to distinguish between them; carefully look at the
log (missing messages)
as soon as
- dvipdfmx supports map file specials
- pdftex is updated around the world
i will change a few defaults in context; currently what works well for new
versions of pdftex may fail in older ones;
> =============texnansi-urw-garamond.map==============
> % You need to add the following line to pdftex.cfg:
> %
> % map +texnansi-urw-garamond.map
> %
^^^ this is no longer valid in newer versions of pdftex
> If there are better/more aesthetic choices for sans and math, let me know-)
you may want to apply rscale=... for sans, mono and math
> Have fun with Garamond!
indeed, these are the steps!
concerning platform fonts ... i'll put a zip on the website with the metrics
(that i so far generated); the only difference there is that you need to make an
afm file from the ttf and that you need to add the platform font path to the
truetype paths etc
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~2005-04-03 20:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-03 0:15 Idris Samawi Hamid
2005-04-03 3:13 ` Ciro Soto
2005-04-03 3:14 ` Ciro Soto
2005-04-03 4:29 ` Ciro Soto
2005-04-03 8:12 ` Peter Münster
2005-04-03 20:07 ` h h extern [this message]
2005-04-03 20:57 ` Willi Egger
2005-04-03 15:58 Idris Samawi Hamid
2005-04-03 18:32 ` Peter Münster
2005-04-03 16:18 Idris Samawi Hamid
2005-04-03 20:23 Idris Samawi Hamid
2005-04-04 17:16 ` Peter Münster
2005-04-04 19:41 ` Hans Hagen
2005-04-05 6:05 ` Peter Münster
2005-04-03 21:13 Idris Samawi Hamid
2005-04-05 14:54 Idris Samawi Hamid
2005-04-05 17:19 ` Peter Münster
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=42504D01.3070207@wxs.nl \
--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).