ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "John R. Culleton" <john@wexfordpress.com>
Cc: Hans Hagen <pragma@wxs.nl>
Subject: Re: newest version on teTeX-3.0
Date: Sat, 4 Jun 2005 08:50:00 +0000	[thread overview]
Message-ID: <200506040850.00612.john@wexfordpress.com> (raw)
In-Reply-To: <42A1806C.1030701@wxs.nl>

On Saturday 04 June 2005 10:20 am, Hans Hagen wrote:
>
> i'm not familiar with updmap
>
> (dvipdfm works ok now, is there a mapfile loading special in dvips?)
>
> Hans
Updmap is a new method of updating all the various font
configuration files on a TeX distribution. It exists on my
TeXLive distro and also my Slackware TeX distro (presumably tetex.) 

Here is a condensed version of the man page:
--------------------------------------------------------------
 updmap  is  a utility that creates font configuration files for
dvips(1), pdftex(1), xdvi(1), ps2pk(1), gsftopk(1), dvipdfm(1)
and  (soon)  dvipdfmx(1).   In  an  ideal world,  updmap  would
be  unnecessary -- each of these programs would read the same
configuration file to learn what fonts are available and how they
should be treated.  As  things stand, however, each of these
tools has subtly different requirements and thereby needs its own
font configuration file.  updmap  creates  font  configuration
files  for  all  of these programs from a single source, allowing
you to easily keep all the different configuration files in sync.

       updmap reads a configuration file, updmap.cfg(5) and,
depending on the options specified in that file and on the
command line, updmap will write generated map files to a
directory of your choosing (via one of the --*outputdir options),
or automatically determine  where  to  place the files.  In the
latter case, it tries to use the tree where the variable TEXMFVAR
points to.  When used with the options --edit,  --setoption,
--enable, --disable, or --syncwithtrees, updmap will first write
updmap.cfg(5) and regenerate the map files only if this file has
been changed.                                                                         
-------------------------------------------------------------
As previously posted I add a line to updmap.cfg asking it to
look for plus.map. Then I add/delete etc. font statements to
that file. When run updmap then updates all the other files used by various
tex variants as described above. 
 
-- 

John Culleton

  reply	other threads:[~2005-06-04  8:50 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-03 21:07 Peter Münster
2005-06-04 10:20 ` Hans Hagen
2005-06-04  8:50   ` John R. Culleton [this message]
2005-06-04 14:05     ` Hans Hagen
2005-06-04 19:17   ` Peter Münster
2005-06-04 19:24     ` Taco Hoekwater
2005-06-05  6:14       ` Peter Münster
2005-06-04 21:30     ` Hans Hagen
2005-06-05  6:15       ` Peter Münster
2005-06-05 17:33     ` Taco Hoekwater
2005-06-07 17:25       ` Peter Münster
2005-06-07 17:58         ` Taco Hoekwater
2005-06-07 20:01           ` Peter Münster
2005-06-07 21:42             ` Taco Hoekwater
2005-06-07 21:43               ` Taco Hoekwater
2005-06-08  7:38                 ` Hans Hagen
2005-06-08 16:33                   ` Tobias Burnus
2005-06-08 20:41                     ` Hans Hagen
2005-06-08 16:41                 ` Peter Münster
2005-06-07 20:07       ` Patrick Gundlach
2005-06-07 21:31         ` Taco Hoekwater
2005-06-08  7:32         ` Hans Hagen
2005-06-08  7:45           ` Patrick Gundlach
2005-06-08 12:47             ` Hans Hagen
2005-06-08 12:51               ` Patrick Gundlach
2005-06-08 14:16                 ` Hans Hagen

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=200506040850.00612.john@wexfordpress.com \
    --to=john@wexfordpress.com \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.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).