From - Wed May  1 00:39:27 2002
Return-Path: <cswingle@iarc.uaf.edu>
Received: from nika.frontier.iarc.uaf.edu (nika.frontier.iarc.uaf.edu
    [137.229.94.16]) by nef.ens.fr (8.10.1/1.01.28121999) with ESMTP id
    g3UMdGa93184 for <metafont@ens.fr>; Wed, 1 May 2002 00:39:17 +0200 (CEST)
Received: by nika.frontier.iarc.uaf.edu (Postfix, from userid 1112) id
    DCC5C14115; Tue, 30 Apr 2002 14:39:25 -0800 (AKDT)
Date: Tue, 30 Apr 2002 14:39:25 -0800
From: Christopher Swingley <cswingle@iarc.uaf.edu>
To: metafont@ens.fr
Message-Id: <20020430223925.GA24146@iarc.uaf.edu>
Mail-Followup-To: metafont@ens.fr
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.28i
X-Url: [http://www.frontier.iarc.uaf.edu/~cswingle/]
X-Editor: VIM 6.1 [http://www.vim.org]
X-Virus-Scanner: AMaVis 0.2.0-pre6 / Virus Scan
X-Loop: metafont@nef.ens.fr
X-Sequence: 535
Precedence: list
Subject: [metafont] Metapost font problem

Hello!

I'm trying to use metapost to generate a figure which I will include
in a TeX document to be run through pdftex.  In order to do so, I
need to convert the metapost figure that is generated into a PDF file.
I use epstopdf for this, which (I believe) uses Ghostscript to perform
the conversion.

If I create a simple metapost file:

    beginfig(5);
    boxit.box(btex foobar etex);
    drawboxed(box);
    endfig;
    end

and then do:

    $ mpost foo
    $ epstopdf foo.5

I get "Error: /undefined in cmr10" and a bunch more output from
Ghostscript (AFPL 7.04).  I've tried adding:

    prologues:=2;

to the beginning of the metapost file, but when I do this, the font
in the file (EPS and PDF) isn't Computer Modern Roman, but looks
something like Courier.

Do I have an installation problem?  Is this not possible using
metapost?  Any other suggestions?

Thanks,

Chris
-- 
Christopher S. Swingley           phone: 907-474-2689
Computer Systems Manager          email: cswingle@iarc.uaf.edu
IARC -- Frontier Program          GPG and PGP keys at my web page:
University of Alaska Fairbanks    www.frontier.iarc.uaf.edu/~cswingle


From - Wed May  1 01:33:06 2002
Return-Path: <listmail@lipman.org>
Received: from sphere.niddk.nih.gov (sphere.niddk.nih.gov [128.231.4.194])
    by nef.ens.fr (8.10.1/1.01.28121999) with ESMTP id g3UNWwa99722 for
    <metafont@ens.fr>; Wed, 1 May 2002 01:32:58 +0200 (CEST)
Received: (from lipman@localhost) by sphere.niddk.nih.gov
    (8.10.2+Sun/8.10.2) id g3UNWvK10679 for metafont@ens.fr; Tue,
    30 Apr 2002 19:32:57 -0400 (EDT)
Date: Tue, 30 Apr 2002 19:32:57 -0400 (EDT)
From: Everett Lipman <listmail@lipman.org>
Message-Id: <200204302332.g3UNWvK10679@sphere.niddk.nih.gov>
To: metafont@ens.fr
Subject: [metafont] Metapost font problem
X-Virus-Scanner: AMaVis 0.2.0-pre6 / Virus Scan
X-Loop: metafont@nef.ens.fr
X-Sequence: 536
Precedence: list

Chris,

You need to have dvips include the fonts for you.  Try
running this script on your output file.

Everett Lipman


#!/bin/sh

#
# mpps - add fonts to raw metapost output
#
# usage: mpps filename
#
# 2 September 1998  Everett Lipman
#
# This program is in the public domain.
#

TMPFILE="mpps$$"

echo ""

if [ "$1" = "" ]
then
   echo "I need a filename, please."
   echo ""
   exit 1
fi

if [ ! -f "${1}.1" ]
then
   if [ ! -f "$1" ]
   then
      echo "${1}[.1]: file not found."
      echo ""
      exit 1
   else filename="$1"
   fi
else
   filename="${1}.1"
fi

vsize=`grep '%%BoundingBox:' $filename | awk '{print $5-$3}'`

sed 's/^X//' << \EOF > $TMPFILE.tex
X\nopagenumbers
X\vbox to 10 true in
X{
X\vss
EOF
echo "\special{psfile=$filename hoffset=-72}" >> $TMPFILE.tex
sed 's/^X//' << \EOF >> $TMPFILE.tex
X}
X\end
EOF

tex $TMPFILE

dvips -o $1.ps $TMPFILE

rm -f $TMPFILE.*

echo ""


From - Wed May  1 16:03:11 2002
Return-Path: <jim@joshua.smcvt.edu>
Received: from joshua.smcvt.edu (joshua.smcvt.edu [192.80.64.209]) by
    nef.ens.fr (8.10.1/1.01.28121999) with ESMTP id g41E2xa97947 for
    <metafont@ens.fr>; Wed, 1 May 2002 16:02:59 +0200 (CEST)
Received: (from jim@localhost) by joshua.smcvt.edu (8.9.3/8.9.3) id
    KAA05545; Wed, 1 May 2002 10:02:38 -0400
Date: Wed, 1 May 2002 10:02:38 -0400
Message-Id: <200205011402.KAA05545@joshua.smcvt.edu>
X-Authentication-Warning: joshua.smcvt.edu: jim set sender to
    jim@joshua.smcvt.edu using -f
From: Jim Hefferon <jim@joshua.smcvt.edu>
To: cswingle@iarc.uaf.edu
Cc: metafont@ens.fr
In-Reply-To: <20020430223925.GA24146@iarc.uaf.edu> (message from
    Christopher Swingley on Tue, 30 Apr 2002 14:39:25 -0800)
Subject: Re: [metafont] Metapost font problem
References: <20020430223925.GA24146@iarc.uaf.edu>
X-Virus-Scanner: AMaVis 0.2.0-pre6 / Virus Scan
X-Loop: metafont@nef.ens.fr
X-Sequence: 537
Precedence: list

   I'm trying to use metapost to generate a figure which I will include
   in a TeX document to be run through pdftex.  In order to do so, I
   need to convert the metapost figure that is generated into a PDF file.

Are you sure?

Is there a reason why this

  \documentclass{article}
  \usepackage{graphics}
  \begin{document}
  Hello.
  \begin{center}
    \includegraphics{foo.mps}
  \end{center}
  Goodbye.
  \end{document}

won't do for you, once you have renamed foo.5 to foo.mps? 

Jim Hefferon


From - Wed May  1 17:02:22 2002
Return-Path: <cswingle@iarc.uaf.edu>
Received: from nika.frontier.iarc.uaf.edu (nika.frontier.iarc.uaf.edu
    [137.229.94.16]) by nef.ens.fr (8.10.1/1.01.28121999) with ESMTP id
    g41F2Ea04400 for <metafont@ens.fr>; Wed, 1 May 2002 17:02:14 +0200 (CEST)
Received: by nika.frontier.iarc.uaf.edu (Postfix, from userid 1112) id
    F0F3513E55; Wed,  1 May 2002 07:02:28 -0800 (AKDT)
Date: Wed, 1 May 2002 07:02:28 -0800
From: Christopher Swingley <cswingle@iarc.uaf.edu>
To: metafont@ens.fr
Subject: Re: [metafont] Metapost font problem
Message-Id: <20020501150228.GB30766@iarc.uaf.edu>
Mail-Followup-To: metafont@ens.fr
References: <20020430223925.GA24146@iarc.uaf.edu>
    <200205011402.KAA05545@joshua.smcvt.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200205011402.KAA05545@joshua.smcvt.edu>
User-Agent: Mutt/1.3.28i
X-Url: [http://www.frontier.iarc.uaf.edu/~cswingle/]
X-Editor: VIM 6.1 [http://www.vim.org]
X-Virus-Scanner: AMaVis 0.2.0-pre6 / Virus Scan
X-Loop: metafont@nef.ens.fr
X-Sequence: 538
Precedence: list

* Jim Hefferon <jim@joshua.smcvt.edu> [2002-May-01 06:02 AKDT]:
>    I'm trying to use metapost to generate a figure which I will include
>    in a TeX document to be run through pdftex.  In order to do so, I
>    need to convert the metapost figure that is generated into a PDF file.
> 
> Are you sure?
> 
> Is there a reason why this
> 
>   \documentclass{article}
>   \usepackage{graphics}
>   \begin{document}
>   Hello.
>   \begin{center}
>     \includegraphics{foo.mps}
>   \end{center}
>   Goodbye.
>   \end{document}
> 
> won't do for you, once you have renamed foo.5 to foo.mps? 

The reason is that pdftex can't include PostScript -- all included
figures need to be converted to PDF files:

    $ pdftex foo
    (/usr/share/texmf/tex/latex/graphics/dvips.def))) <foo.mps>
    [1{/usr/share/texmf /dvips/config/pdftex.map}
    Non-PDF special ignored!] )

It does produce a PDF file, but it doesn't contain the graphic.

* Everett Lipman <lipman@helix.nih.gov> [2002-Apr-30 15:29 AKDT]:
> You need to have dvips include the fonts for you.  Try running this
> script on your output file.

Thanks for the script!  It does work, but it doesn't help with PDF.
For some reason converting the PostScript image that's produced to
PDF results in a poor quality pixelated version of the font in the
PDF file (as viewed on the screen), and when this graphic is embedded
in a TeX document, run through pdftex, and printed, the text doesn't
print at all.

Chris
-- 
Christopher S. Swingley           phone: 907-474-2689
Computer Systems Manager          email: cswingle@iarc.uaf.edu
IARC -- Frontier Program          GPG and PGP keys at my web page:
University of Alaska Fairbanks    www.frontier.iarc.uaf.edu/~cswingle


From - Wed May  1 17:23:26 2002
Return-Path: <jim@joshua.smcvt.edu>
Received: from joshua.smcvt.edu (joshua.smcvt.edu [192.80.64.209]) by
    nef.ens.fr (8.10.1/1.01.28121999) with ESMTP id g41FNCa07126 for
    <metafont@ens.fr>; Wed, 1 May 2002 17:23:12 +0200 (CEST)
Received: (from jim@localhost) by joshua.smcvt.edu (8.9.3/8.9.3) id
    LAA05964; Wed, 1 May 2002 11:23:01 -0400
Date: Wed, 1 May 2002 11:23:01 -0400
Message-Id: <200205011523.LAA05964@joshua.smcvt.edu>
X-Authentication-Warning: joshua.smcvt.edu: jim set sender to
    jim@joshua.smcvt.edu using -f
From: Jim Hefferon <jim@joshua.smcvt.edu>
To: cswingle@iarc.uaf.edu
Cc: metafont@ens.fr
In-Reply-To: <20020501150228.GB30766@iarc.uaf.edu> (message from
    Christopher Swingley on Wed, 1 May 2002 07:02:28 -0800)
Subject: Re: [metafont] Metapost font problem
References: <20020430223925.GA24146@iarc.uaf.edu>
    <200205011402.KAA05545@joshua.smcvt.edu>
    <20020501150228.GB30766@iarc.uaf.edu>
X-Virus-Scanner: AMaVis 0.2.0-pre6 / Virus Scan
X-Loop: metafont@nef.ens.fr
X-Sequence: 539
Precedence: list


   The reason is that pdftex can't include PostScript -- all included
   figures need to be converted to PDF files:

       $ pdftex foo
       (/usr/share/texmf/tex/latex/graphics/dvips.def))) <foo.mps>
       [1{/usr/share/texmf /dvips/config/pdftex.map}
       Non-PDF special ignored!] )

   It does produce a PDF file, but it doesn't contain the graphic.

I don't know what setup you have.  I have a routine teTeX (the Unix 
distribution) on a Linux machine.  This file test.mp
...................................
verbatimtex
%&latex
\documentclass{book}
\begin{document}
etex

input boxes;

beginfig(5);
%boxit.box(btex foobar etex);
%drawboxed(box);
pickup pencircle scaled 1pt;
draw (0in,0in)--(1in,1in); 

endfig;
end
...............................
when run with `mpost test.mp' and followed by `cp test.5 test.mps'
will produced a graphic that pdflatex knew what to do with.
(I agree that pdflatex has to do something fancy with it, but it
doesn't matter.)  I ran test.tex
.............................
\documentclass{article}
\usepackage{graphics}
\begin{document}
Hello.
\begin{center}
  \includegraphics{test.mps}
\end{center}
Goodbye.
\end{document}
..............................
with pdflatex it produced output that Adobe Reader rendered
as including the graphic.

Jim


From - Wed May  1 18:25:11 2002
Return-Path: <mcquaid@ptah.u.arizona.edu>
Received: from ptah.u.arizona.edu (ptah.u.Arizona.EDU [128.196.133.224])
    by nef.ens.fr (8.10.1/1.01.28121999) with ESMTP id g41GP0a14063 for
    <metafont@ens.fr>; Wed, 1 May 2002 18:25:00 +0200 (CEST)
Received: (from mcquaid@localhost) by ptah.u.arizona.edu
    (8.11.6+Sun/8.10.2) id g41GOjI22884; Wed, 1 May 2002 09:24:45 -0700 (MST)
Date: Wed, 1 May 2002 09:24:45 -0700
From: Mick McQuaid <mcquaid@u.arizona.edu>
To: Jim Hefferon <jim@joshua.smcvt.edu>
Cc: cswingle@iarc.uaf.edu, metafont@ens.fr
Subject: Re: [metafont] Metapost font problem
Message-Id: <20020501092445.A19973@U.Arizona.EDU>
References: <20020430223925.GA24146@iarc.uaf.edu>
    <200205011402.KAA05545@joshua.smcvt.edu>
    <20020501150228.GB30766@iarc.uaf.edu>
    <200205011523.LAA05964@joshua.smcvt.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <200205011523.LAA05964@joshua.smcvt.edu>; from
    jim@joshua.smcvt.edu on Wed, May 01, 2002 at 11:23:01AM -0400
X-Virus-Scanner: AMaVis 0.2.0-pre6 / Virus Scan
X-Loop: metafont@nef.ens.fr
X-Sequence: 540
Precedence: list

After I process a mp file, file.mp, it produces
outputs like file.1, file.2, etc.

I include each of these in a pdflatex doc using
the macro convertMPtoPDF, which is defined in
pdftex.def, and available in many packages,
including graphics.sty, making it available to the
poster below.  Looking at the file pdftex.def, it
looks like it is invoked automatically if I rename
my metapost file with extension .mps, instead of
.1, .2, .3, or whatever.

Here is an example of how I invoke it manually,
having first loaded a package, such as
pdfscreen.sty, color.sty, or graphics.sty,
that includes it:

\begin{figure}
\begin{center}
\hfil\convertMPtoPDF{nixondiamonds.1}{1.00}{1.00}\hfil
\end{center}
\caption{part-whole and generalization relationships}
\label{fig:marriage01}
\end{figure}

If I rename the metapost file to
nixondiamonds.mps, I can say instead:

\begin{figure}
\begin{center}
\hfil\includegraphics{nixondiamonds.mps}{1.00}{1.00}\hfil
\end{center}
\caption{part-whole and generalization relationships}
\label{fig:marriage01}
\end{figure}

A possibly better alternative is to do what it
says in m-metapo.tex.  I quote a comment from that
file here.  I think it may solve some font
problems, but have no more time to look at it
today!

%D An example of using this module is given below: 
%D 
%D \starttypen
%D \documentclass[10pt]{article}
%D 
%D \usepackage{graphicx}
%D \usepackage{m-metapo}
%D 
%D \begin{document}
%D   \includeMPgraphics{somefile.1}
%D   \includeMPgraphics[angle=90]{somefile.2}
%D \end{document}
%D \stoptypen
%D
%D This module needs \type {supp-mps} and \type
%{supp-mis}, 
%D that both are present in the \CONTEXT\ path.
%D
%D Pleas do not forget to say \type {prologues:=2}
%at the 
%D top of the metapost file!
%D 
%D For non \LATEX\ (and \CONTEXT) users we provide
%an 
%D alternative inclusion macro. This one has no
%optional 
%D arguments. 

... regarding a message from Jim Hefferon on May 01:
> 
>    The reason is that pdftex can't include PostScript -- all included
>    figures need to be converted to PDF files:
> 
>        $ pdftex foo
>        (/usr/share/texmf/tex/latex/graphics/dvips.def))) <foo.mps>
>        [1{/usr/share/texmf /dvips/config/pdftex.map}
>        Non-PDF special ignored!] )
> 
>    It does produce a PDF file, but it doesn't contain the graphic.
> 
> I don't know what setup you have.  I have a routine teTeX (the Unix 
> distribution) on a Linux machine.  This file test.mp
> ...................................
> verbatimtex
> %&latex
> \documentclass{book}
> \begin{document}
> etex
> 
> input boxes;
> 
> beginfig(5);
> %boxit.box(btex foobar etex);
> %drawboxed(box);
> pickup pencircle scaled 1pt;
> draw (0in,0in)--(1in,1in); 
> 
> endfig;
> end
> ...............................
> when run with `mpost test.mp' and followed by `cp test.5 test.mps'
> will produced a graphic that pdflatex knew what to do with.
> (I agree that pdflatex has to do something fancy with it, but it
> doesn't matter.)  I ran test.tex
> .............................
> \documentclass{article}
> \usepackage{graphics}
> \begin{document}
> Hello.
> \begin{center}
>   \includegraphics{test.mps}
> \end{center}
> Goodbye.
> \end{document}
> ..............................
> with pdflatex it produced output that Adobe Reader rendered
> as including the graphic.
> 
> Jim
> 

-- 
Mick McQuaid, mcquaid@u.arizona.edu
              520-621-4074 office / voice mail


From - Wed May  1 18:55:47 2002
Return-Path: <cswingle@iarc.uaf.edu>
Received: from nika.frontier.iarc.uaf.edu (nika.frontier.iarc.uaf.edu
    [137.229.94.16]) by nef.ens.fr (8.10.1/1.01.28121999) with ESMTP id
    g41GtYa17196 for <metafont@ens.fr>; Wed, 1 May 2002 18:55:34 +0200 (CEST)
Received: by nika.frontier.iarc.uaf.edu (Postfix, from userid 1112) id
    B5A9C13E55; Wed,  1 May 2002 08:55:46 -0800 (AKDT)
Date: Wed, 1 May 2002 08:55:46 -0800
From: Christopher Swingley <cswingle@iarc.uaf.edu>
To: metafont@ens.fr
Subject: Re: [metafont] Metapost font problem
Message-Id: <20020501165546.GA31654@iarc.uaf.edu>
Mail-Followup-To: metafont@ens.fr
References: <20020430223925.GA24146@iarc.uaf.edu>
    <200205011402.KAA05545@joshua.smcvt.edu>
    <20020501150228.GB30766@iarc.uaf.edu>
    <200205011523.LAA05964@joshua.smcvt.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200205011523.LAA05964@joshua.smcvt.edu>
User-Agent: Mutt/1.3.28i
X-Url: [http://www.frontier.iarc.uaf.edu/~cswingle/]
X-Editor: VIM 6.1 [http://www.vim.org]
X-Virus-Scanner: AMaVis 0.2.0-pre6 / Virus Scan
X-Loop: metafont@nef.ens.fr
X-Sequence: 541
Precedence: list

* Jim Hefferon <jim@joshua.smcvt.edu> [2002-May-01 07:23 AKDT]:
> with pdflatex it produced output that Adobe Reader rendered
> as including the graphic.

You're right.  pdflatex does seem to work here.  I think it's because of
this magic:

    loading : Context Support Macros / PDF) [MP to PDF test.mps]

unfortunately, when I use pdftex instead, the magic doesn't happen and I
get 'Non-PDF special ignored!'.  But I figure out the trick:

    \input supp-pdf
    Hello.

    \convertMPtoPDF{test.mps}{1}{1}

    Goodbye.
    \vfill\eject\bye

Thanks for all the replies!

Chris
-- 
Christopher S. Swingley           phone: 907-474-2689
Computer Systems Manager          email: cswingle@iarc.uaf.edu
IARC -- Frontier Program          GPG and PGP keys at my web page:
University of Alaska Fairbanks    www.frontier.iarc.uaf.edu/~cswingle


From - Thu May  2 17:34:25 2002
Return-Path: <luecking@uark.edu>
Received: from mail.uark.edu (mail.uark.edu [130.184.5.107]) by nef.ens.fr
    (8.10.1/1.01.28121999) with ESMTP id g42FYFa87366 for <metafont@ens.fr>;
    Thu, 2 May 2002 17:34:15 +0200 (CEST)
Received: from comp.uark.edu ([130.184.5.197]) by mail.uark.edu (Netscape
    Messaging Server 4.15) with ESMTP id GVHPWU00.U82 for <metafont@ens.fr>;
    Thu, 2 May 2002 10:34:06 -0500
Received: (from luecking@localhost) by comp.uark.edu (8.11.6/8.11.6) id
    g42FVfl20288; Thu, 2 May 2002 10:31:41 -0500 (CDT)
Date: Thu, 2 May 2002 10:31:41 -0500 (CDT)
From: "Daniel Luecking" <luecking@uark.edu>
To: Christopher Swingley <cswingle@iarc.uaf.edu>
Cc: <metafont@ens.fr>
Subject: Re: [metafont] Metapost font problem
In-Reply-To: <20020501165546.GA31654@iarc.uaf.edu>
Message-Id: <Pine.SOL.4.33.0205021015050.13962-100000@comp.uark.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanner: AMaVis 0.2.0-pre6 / Virus Scan
X-Loop: metafont@nef.ens.fr
X-Sequence: 542
Precedence: list

On Wed, 1 May 2002, Christopher Swingley wrote:

> * Jim Hefferon <jim@joshua.smcvt.edu> [2002-May-01 07:23 AKDT]:
> > with pdflatex it produced output that Adobe Reader rendered
> > as including the graphic.
>
> You're right.  pdflatex does seem to work here.  I think it's because of
> this magic:
>
>     loading : Context Support Macros / PDF) [MP to PDF test.mps]
>
> unfortunately, when I use pdftex instead, the magic doesn't happen and I
> get 'Non-PDF special ignored!'.  But I figure out the trick:
>
>     \input supp-pdf
>     Hello.
>
>     \convertMPtoPDF{test.mps}{1}{1}
>
>     Goodbye.
>     \vfill\eject\bye
>

It would seem you were originally using the plain TeX graphics bundle
from David Carlisle. (You really should reveal such info at some point.)
The problem with that is it's use of dvips as the default driver. You
can see in the .log file where dvips.def is being input:
     $ pdftex foo
    (/usr/share/texmf/tex/latex/graphics/dvips.def))) <foo.mps>
    [1{/usr/share/texmf /dvips/config/pdftex.map}
    Non-PDF special ignored!] )

This comes from the following line in graphicx.tex:

  \def\Gin@driver{dvips.def}

You can delete this line and rely on graphics.cfg to select the correct
driver definitions, or you can wrap it with some conditional code and
select yourself:

  \input ifpdf.sty
  \ifpdf
    \def\Gin@driver{pdftex.def}
  \else
    \def\Gin@driver{dvips.def}
  \fi

The file graphics.cfg does something similar if properly written.

This fix presumes that one has a fairly recent pdftex.def, since older
versions were incompatable with the file miniltx.tex input by
Carlisle's graphicx.tex.

-- 
Dan Luecking                           Dept. of Mathematical Sciences
luecking@uark.edu                      University of Arkansas
http://comp.uark.edu/~luecking/        Fayetteville, AR 72101



From - Fri May  3 18:55:59 2002
Return-Path: <smuelas@mecanica.upm.es>
Received: from filemon.mecanica.upm.es (filemon.mecanica.upm.es
    [138.100.66.1]) by nef.ens.fr (8.10.1/1.01.28121999) with ESMTP id
    g43Gtpa49361 for <metafont@ens.fr>; Fri, 3 May 2002 18:55:51 +0200 (CEST)
Received: from [138.100.66.105] (helo=simux.mecanica.upm.es) by
    filemon.mecanica.upm.es with esmtp (Exim 3.33 #1 (Debian)) id
    173gLV-00018s-00; Fri, 03 May 2002 18:55:49 +0200
From: SMuelas <smuelas@mecanica.upm.es>
To: metagraf@eGroups.com
Cc: metafont@ens.fr
Content-Type: text/plain; charset=ISO-8859-1
X-Mailer: Evolution/1.0.2-5mdk
Date: 03 May 2002 18:56:48 +0200
Message-Id: <1020445008.29407.10.camel@simux.mecanica.upm.es>
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-Mime-Autoconverted: from quoted-printable to 8bit by nef.ens.fr id
    g43Gtpa49361
X-Virus-Scanner: AMaVis 0.2.0-pre6 / Virus Scan
X-Loop: metafont@nef.ens.fr
X-Sequence: 543
Precedence: list
Subject: [metafont] New and first stable release of MG - Nueva y primera
    versión stable de MG

Today a new release of METAGRAF has been made available for downloading
in the validate page: http://w3.mecanica.upm.es/metapost/metagraf.php
This is the first stable version ( 1.2 ) and will remain unchanged
during the next six months. It includes the User's Manual in English and
the all new "geometrically-attached" objects that will be a most in the
future.
---------

A partir de este momento está disponible en la página de METAGRAF que se
señala arriba, la última versión con "vocación" de version estable y
número 1.2. Incluye el Manual completo en Inglés y los nuevos objetos
recién desarrollados para los que se preservan las relaciones
geométricas elegidas y que se ampliarán de forma importante en el
futuro.
-- 
Santiago Muelas (Depto. de Mecánica)         
http://w3.mecanica.upm.es/~smuelas
ETSI de Caminos, Canales y Puertos (U.P.M)    smuelas@mecanica.upm.es
Dr.Aranguren s/n - Ciudad Universitaria       Tf. 91 336 6659
MADRID 28040


From - Sat May  4 01:30:14 2002
Return-Path: <Denis.Roegel@loria.fr>
Received: from lorraine.loria.fr (lorraine.loria.fr [152.81.1.17]) by
    nef.ens.fr (8.10.1/1.01.28121999) with ESMTP id g43NU4a92604 for
    <metafont@ens.fr>; Sat, 4 May 2002 01:30:05 +0200 (CEST)
Received: from bar.loria.fr (bar.loria.fr [152.81.2.13]) by
    lorraine.loria.fr (8.9.3/8.9.3/8.9.3/JCG-DG) with ESMTP id BAA03067;
    Sat, 4 May 2002 01:30:03 +0200 (MET DST)
Received: (from roegel@localhost) by bar.loria.fr
    (8.9.3/8.9.3/8.9.3-client/JCG) id BAA21970; Sat, 4 May 2002 01:30:02 +0200
    (MET DST)
Date: Sat, 4 May 2002 01:30:02 +0200
From: "Denis B. Roegel" <Denis.Roegel@loria.fr>
To: SMuelas <smuelas@mecanica.upm.es>
Cc: metagraf@eGroups.com, metafont@ens.fr,
    "Denis B. Roegel" <roegel@lorraine.loria.fr>
Subject: Re: [metafont] New and first stable release of MG - Nueva y
    primera versión stable de MG
Message-Id: <20020504013002.A21654@bar.loria.fr>
References: <1020445008.29407.10.camel@simux.mecanica.upm.es>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.1i
In-Reply-To: <1020445008.29407.10.camel@simux.mecanica.upm.es>;
    from smuelas@mecanica.upm.es on Fri, May 03, 2002 at 06:56:48PM +0200
X-Virus-Scanner: AMaVis 0.2.0-pre6 / Virus Scan
X-Loop: metafont@nef.ens.fr
X-Sequence: 544
Precedence: list

On Fri, May 03, 2002 at 06:56:48PM +0200, SMuelas wrote:
> Today a new release of METAGRAF has been made available for downloading
> in the validate page: http://w3.mecanica.upm.es/metapost/metagraf.php
> This is the first stable version ( 1.2 ) and will remain unchanged
> during the next six months. It includes the User's Manual in English and
> the all new "geometrically-attached" objects that will be a most in the
> future.

Hi, can you provide a link towards a PS or PDF version of your manual
on your web page? I think it is important that one can browse the
documentation without having to download the whole package.

Thanks,

Denis Roegel


From - Sun May  5 19:07:11 2002
Return-Path: <pragma@wxs.nl>
Received: from mail.solcon.nl (mail.solcon.nl [212.45.33.11]) by
    nef.ens.fr (8.10.1/1.01.28121999) with ESMTP id g45H6xH18253 for
    <metafont@ens.fr>; Sun, 5 May 2002 19:06:59 +0200 (CEST)
Received: from server-1.pragma-ade.nl ([212.45.58.16]) by mail.solcon.nl
    (8.11.2/8.11.0) with ESMTP id g45H6l212225; Sun, 5 May 2002 19:06:47 +0200
Received: from laptop-2.wxs.nl (localhost [127.0.0.1]) by
    server-1.pragma-ade.nl (8.11.6/8.11.6) with ESMTP id g45H6q230318;
    Sun, 5 May 2002 19:06:52 +0200
Message-Id: <5.1.0.14.1.20020502095835.0371cad8@remote-1>
X-Sender: hagen@remote-1
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 02 May 2002 10:00:06 +0200
To: Christopher Swingley <cswingle@iarc.uaf.edu>
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: [metafont] Metapost font problem
Cc: metafont@ens.fr
In-Reply-To: <20020501165546.GA31654@iarc.uaf.edu>
References: <200205011523.LAA05964@joshua.smcvt.edu>
    <20020430223925.GA24146@iarc.uaf.edu>
    <200205011402.KAA05545@joshua.smcvt.edu>
    <20020501150228.GB30766@iarc.uaf.edu>
    <200205011523.LAA05964@joshua.smcvt.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Ravmilter-Version: 8.3.0(snapshot 20010925) (mail.solcon.nl)
X-Virus-Scanner: AMaVis 0.2.0-pre6 / Virus Scan
X-Loop: metafont@nef.ens.fr
X-Sequence: 545
Precedence: list

At 08:55 AM 5/1/2002 -0800, Christopher Swingley wrote:
>* Jim Hefferon <jim@joshua.smcvt.edu> [2002-May-01 07:23 AKDT]:
> > with pdflatex it produced output that Adobe Reader rendered
> > as including the graphic.
>
>You're right.  pdflatex does seem to work here.  I think it's because of
>this magic:
>
>     loading : Context Support Macros / PDF) [MP to PDF test.mps]
>
>unfortunately, when I use pdftex instead, the magic doesn't happen and I
>get 'Non-PDF special ignored!'.  But I figure out the trick:
>
>     \input supp-pdf
>     Hello.
>
>     \convertMPtoPDF{test.mps}{1}{1}
>
>     Goodbye.
>     \vfill\eject\bye
>
>Thanks for all the replies!

In the context distribution (and on tex live) there is the special

mptopdf

format, which uses supp-pdf to convert mp graphics into pdf; an added bonus 
is that it supports the metafun macros that handle things like graphic 
inclusion in mp, shading, transparency, cmyk color spaces and alike (see 
www.pragma-ade.com -> big picture -> showcase -> manuals -> metafun / mptopdf

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
-------------------------------------------------------------------------
                        information: http://www.pragma-ade.com/roadmap.pdf
                     documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------


From - Mon May 13 00:33:22 2002
Return-Path: <beesley@wanadoo.fr>
Received: from mel-rto4.wanadoo.fr (smtp-out-4.wanadoo.fr [193.252.19.23])
    by nef.ens.fr (8.10.1/1.01.28121999) with ESMTP id g4CMXDH52085 for
    <metafont@ens.fr>; Mon, 13 May 2002 00:33:13 +0200 (CEST)
Received: from mel-rta10.wanadoo.fr (193.252.19.193) by
    mel-rto4.wanadoo.fr (6.5.007) id 3CDBAB2D0010D676 for metafont@ens.fr;
    Mon, 13 May 2002 00:33:12 +0200
Received: from localhost (80.14.224.53) by mel-rta10.wanadoo.fr (6.5.007)
    id 3CD0C9A7005782EA for metafont@ens.fr; Mon, 13 May 2002 00:33:12 +0200
Date: Mon, 13 May 2002 00:34:15 +0200
Mime-Version: 1.0 (Apple Message framework v481)
Content-Type: text/plain; charset=US-ASCII; format=flowed
From: Kenneth Beesley <beesley@wanadoo.fr>
To: metafont <metafont@ens.fr>
Content-Transfer-Encoding: 7bit
Message-Id: <63A6D00B-65F8-11D6-AA2D-000393454058@wanadoo.fr>
X-Mailer: Apple Mail (2.481)
X-Virus-Scanner: AMaVis 0.2.0-pre6 / Virus Scan
X-Loop: metafont@nef.ens.fr
X-Sequence: 546
Precedence: list
Subject: [metafont] Force (La)TeX to use edited font??


Background:
   METAFONT beginner.
   Working on Mac TiBook with 'mf' distributed with teTeX for OS X.
   Working mostly from the Xfree86/WindowMaker environment.
   I managed, I think, to define a mode for my printer (Epson Stylus 
Photo 895), put it in
	local.mf (which started as modes.mf), and inimf my installation.
   Managed to define a new font for the Deseret Alphabet (a non-roman 
phonemic alphabet).
   I can view the proofs in proof mode.
   Using my new mode, I can generate gf, pk and .tfm files, and install 
the pk and tfm files where they are seen.
   I defined a desalph.sty file, new XXXenc.def file, etc.,  modeled 
mostly on tipa.sty.  In my latex
	source document, I can now do

	\usepackage{desalph}
	...
   	\begin{document}
          ...
   	\begin{DA}  encodings for Deseret characters here, based on the 
shortcut
          entry characters in the TIPA package  \end{DA}

   I can create simple LaTeX files and, using pdflatex, produce .pdf 
documents that contain sections in
	my new font.  I can even print them.  Using 'latex', I can produce 
.dvi and .ps files.


So far so good.

Problem:  I'm still modifying the new font.  If I now modify my .mf 
files, and re-generate
and re-install the Deseret Alphabet pk and .tfm files,  pdflatex seems 
to ignore the new versions.
It's like it has generated its own versions/modification of the fonts 
somewhere, cached them, and
ignores the new files.

Am I doing something obviously wrong?

How can I force latex/pdflatex to use the modified pk and .tfm files?

Thanks,

Ken

ken.beesley@xrce.xerox.com
beesley@wanadoo.fr


From - Mon May 13 03:06:19 2002
Return-Path: <tim@maths.tcd.ie>
Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11])
    by nef.ens.fr (8.10.1/1.01.28121999) with SMTP id g4D167H69312 for
    <metafont@ens.fr>; Mon, 13 May 2002 03:06:07 +0200 (CEST)
Received: from boole.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id
    <aa88572@salmon>; 13 May 2002 02:06:07 +0100 (BST)
Date: Mon, 13 May 2002 02:06:06 +0100
From: Timothy Murphy <tim@maths.tcd.ie>
To: metafont@ens.fr
Subject: Re: [metafont] Force (La)TeX to use edited font??
Message-Id: <20020513010606.GA33543@boole.maths.tcd.ie>
References: <63A6D00B-65F8-11D6-AA2D-000393454058@wanadoo.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <63A6D00B-65F8-11D6-AA2D-000393454058@wanadoo.fr>
User-Agent: Mutt/1.3.25i
Sender: tim@maths.tcd.ie
X-Virus-Scanner: AMaVis 0.2.0-pre6 / Virus Scan
X-Loop: metafont@nef.ens.fr
X-Sequence: 547
Precedence: list

On Mon, May 13, 2002 at 12:34:15AM +0200, Kenneth Beesley wrote:

> How can I force latex/pdflatex to use the modified pk and .tfm files?

I don't know, but you could try saying

kpsewhich foo.tfm

to see where LaTeX/pdfLaTeX finds foo.tfm .
If that doesn't help you could say

kpsewhich --debug=-1 foo.tfm

to see where it looks for it.

-- 
Timothy Murphy  
e-mail: tim@maths.tcd.ie
tel: 086-233 6090
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland


From - Mon May 13 07:13:49 2002
Return-Path: <luecking@uark.edu>
Received: from mail.uark.edu (mail.uark.edu [130.184.5.107]) by nef.ens.fr
    (8.10.1/1.01.28121999) with ESMTP id g4D5DfH96787 for <metafont@ens.fr>;
    Mon, 13 May 2002 07:13:41 +0200 (CEST)
Received: from comp.uark.edu ([130.184.5.197]) by mail.uark.edu (Netscape
    Messaging Server 4.15) with ESMTP id GW1AIS00.901 for <metafont@ens.fr>;
    Mon, 13 May 2002 00:13:40 -0500
Received: (from luecking@localhost) by comp.uark.edu (8.11.6/8.11.6) id
    g4D5Dd405027; Mon, 13 May 2002 00:13:39 -0500 (CDT)
Date: Mon, 13 May 2002 00:13:39 -0500 (CDT)
From: "Daniel Luecking" <luecking@uark.edu>
To: metafont <metafont@ens.fr>
Subject: Re: [metafont] Force (La)TeX to use edited font??
In-Reply-To: <63A6D00B-65F8-11D6-AA2D-000393454058@wanadoo.fr>
Message-Id: <Pine.SOL.4.33.0205122354240.3446-100000@comp.uark.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanner: AMaVis 0.2.0-pre6 / Virus Scan
X-Loop: metafont@nef.ens.fr
X-Sequence: 548
Precedence: list

On Mon, 13 May 2002, Kenneth Beesley wrote:

>
> So far so good.
>
> Problem:  I'm still modifying the new font.  If I now modify my .mf
> files, and re-generate
> and re-install the Deseret Alphabet pk and .tfm files,  pdflatex seems
> to ignore the new versions.
> It's like it has generated its own versions/modification of the fonts
> somewhere, cached them, and
> ignores the new files.

I don't know how pdflatex might do things on teTeX, but in MiKTeX, it
seeks fonts as follows:
It first checks pdftex.cfg for a pk_resolution value. If it fails to
find one, it assumes 72dpi. If it finds one, it uses that value (mine
says "pk_resolution 600"). If it encounters a font that doesn't exist in
scalable form (PS type1 or TrueType font) or that does exist but isn't
in one of its .map files, it attempts to find a .pk font at the above
resolution. If that doesn't exist, it does indeed generate it and
store it away. The odd thing is (in MiKTeX at least) it assumes the
mf mode "ljfour" (this seems to be compiled in and there is no
documented way to change it).

The .pk files, therefore, are stored in $TEXMF/fonts/pk/ljfour/.../dpi72
(or dpi600, or whatever value pk_resolution was). And your own carefully
prepared mode is ignored. On the plus side, pdflatex does seem to check
the current directory for .pk files and does not seem to care what mode
was used to prepare them (or at what dpi). When I am still in the
process of tweaking a font, I keep the .pk files in the current
directory and make sure to test only one magnification at a time since
the extension used in MiKTeX (.pk) doesn't reflect the resolution.

I also only use plain latex, since it doesn't care about .pk files and
dvips is much more well behaved (i.e., is configurable) in its use of
.pk files.


-- 
Dan Luecking                           Dept. of Mathematical Sciences
luecking@uark.edu                      University of Arkansas
http://comp.uark.edu/~luecking/        Fayetteville, AR 72101


From - Mon May 13 09:58:09 2002
Return-Path: <beesley@wanadoo.fr>
Received: from mel-rto1.wanadoo.fr (smtp-out-1.wanadoo.fr
    [193.252.19.188]) by nef.ens.fr (8.10.1/1.01.28121999) with ESMTP id
    g4D7w2H38344 for <metafont@ens.fr>; Mon, 13 May 2002 09:58:02 +0200 (CEST)
Received: from mel-rta7.wanadoo.fr (193.252.19.61) by mel-rto1.wanadoo.fr
    (6.5.007) id 3CD6B879001A586E; Mon, 13 May 2002 09:58:01 +0200
Received: from localhost (80.14.224.53) by mel-rta7.wanadoo.fr (6.5.007)
    id 3CD0C97C005612D9; Mon, 13 May 2002 09:58:01 +0200
Date: Mon, 13 May 2002 09:59:04 +0200
Subject: Re: [metafont] Force (La)TeX to use edited font??
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v481)
From: Kenneth Beesley <beesley@wanadoo.fr>
To: "Daniel Luecking" <luecking@uark.edu>, metafont <metafont@ens.fr>, home <beesley@wanadoo.fr>
Content-Transfer-Encoding: 7bit
In-Reply-To: <Pine.SOL.4.33.0205122354240.3446-100000@comp.uark.edu>
Message-Id: <4B919CC6-6647-11D6-9429-000393454058@wanadoo.fr>
X-Mailer: Apple Mail (2.481)
X-Virus-Scanner: AMaVis 0.2.0-pre6 / Virus Scan
X-Loop: metafont@nef.ens.fr
X-Sequence: 549
Precedence: list


On Monday, May 13, 2002, at 07:13 , Daniel Luecking wrote:

> On Mon, 13 May 2002, Kenneth Beesley wrote:
>
>>
>> So far so good.
>>
>> Problem:  I'm still modifying the new font.  If I now modify my .mf
>> files, and re-generate
>> and re-install the Deseret Alphabet pk and .tfm files,  pdflatex seems
>> to ignore the new versions.
>> It's like it has generated its own versions/modification of the fonts
>> somewhere, cached them, and
>> ignores the new files.
>
> I don't know how pdflatex might do things on teTeX, but in MiKTeX, it
> seeks fonts as follows:
> It first checks pdftex.cfg for a pk_resolution value. If it fails to
> find one, it assumes 72dpi. If it finds one, it uses that value (mine
> says "pk_resolution 600"). If it encounters a font that doesn't exist in
> scalable form (PS type1 or TrueType font) or that does exist but isn't
> in one of its .map files, it attempts to find a .pk font at the above
> resolution. If that doesn't exist, it does indeed generate it and
> store it away. The odd thing is (in MiKTeX at least) it assumes the
> mf mode "ljfour" (this seems to be compiled in and there is no
> documented way to change it).

Dear Mr. Luecking,

Many thanks for your reply.  Each installation is different, 
unfortunately,
and I still don't know what's crucial vs. incidental.  On teTeX, the 
supplied
modes.mf file includes a mode definition for ljfour and the line

localfont := ljfour ;

I _think_ that this is how ljfour is currently "wired in".  But it's 
easily changed.
As I understand things, one is supposed to 'localize' one's mf 
installation,
including:

copying modes.mf to local.mf
adding to local.mf any new mode_defs necessary for your local printer(s)
taking out any mode_defs that are not needed (I found it wise to
      take out just mode_defs, not any of the other definitions)
change the value of localfont;  In my case, I defined a new mode epsspenf
	for my Epson Stylus Photo 895 (1440 x 720 dpi) and set
	localfont := epsspenf

Initialization using the new local.mf file:

      inimf 'plain; input local; dump; bye'

This creates a plain.base file that I installed as 
~/Library/texmf/web2c/mf.base
In this same directory I created safety pointers
	plain.base -> mf.base
	mfw.base -> mf.base
for flavors of (La)TeX that might look for the base file under another 
name.

My desalph.mf source files reside in 
~/Library/texmf/fonts/sources/desalph/*
The ~/Library/texmf/ area is active under teTeX and is searched before
the texmf.local, texmf.macosx, and standard texmf directories.  
~/Library/texmf/ is the
texmf for private additions.

Now I generate real fonts for my printer with the command

mf '\mode=localfont; input  desalph24'

and it dutifully produces fonts at 1440 dpi

         desalph24.1440gf (from which I produce desalph24.1440pk)
and desalph24.tfm.

And these new files got used, when I first invoked pdflatex on my 
testfiles.

> The .pk files, therefore, are stored in $TEXMF/fonts/pk/ljfour/.../dpi72
> (or dpi600, or whatever value pk_resolution was). And your own carefully
> prepared mode is ignored.

I think that my mode is not being ignored.  After producing my new 
fonts, I then 'install'
      desalph24.1440pk  in  ~/Library/texmf/fonts/pk/desalph/
and
     desalph24.tfm  in ~/Library/texmf/fonts/tfm/desalph/

kpsewhich shows that they are indeed being found there.


> On the plus side, pdflatex does seem to check
> the current directory for .pk files and does not seem to care what mode
> was used to prepare them (or at what dpi). When I am still in the
> process of tweaking a font, I keep the .pk files in the current
> directory and make sure to test only one magnification at a time since
> the extension used in MiKTeX (.pk) doesn't reflect the resolution.
>
> I also only use plain latex, since it doesn't care about .pk files and
> dvips is much more well behaved (i.e., is configurable) in its use of
> .pk files.

I'm not sure that I understand this.

In any case, my problem is that if I now re-edit the desalph.mf files, 
and reinstall
desalph24.1440pk and desalph24.tfm, kpsewhich finds the new files, but 
they
don't seem to be used.  My tests get generated with the older version of 
the fonts,
as if pdflatex had generated and cached some other kind of font.  (What 
kind of
font does pdflatex use?)

I somehow need to tell pdflatex to start all over, re-generating any 
files it needs
directly from the new desalph24.1440pk and desalph24.tfm.

Sorry if I sound confused.  I'm still quite new at this.

Ken Beesley
ken.beesley@xrce.xerox.com
beesley@wanadoo.fr


From - Mon May 13 14:26:33 2002
Return-Path: <beebe@sunshine.math.utah.edu>
Received: from sunshine.math.utah.edu (sunshine.math.utah.edu
    [128.110.198.2]) by nef.ens.fr (8.10.1/1.01.28121999) with ESMTP id
    g4DCQMH11652 for <metafont@ens.fr>; Mon, 13 May 2002 14:26:22 +0200 (CEST)
Received: from plot79.math.utah.edu
    (IDENT:pHNzlWDFEdvWzIb5JfmxBIhqWGDKygWv@plot79.math.utah.edu
    [128.110.198.20]) by sunshine.math.utah.edu (8.9.3/8.9.3) with ESMTP id
    GAA07491; Mon, 13 May 2002 06:26:19 -0600 (MDT)
Received: (from beebe@localhost) by plot79.math.utah.edu (8.9.3/8.9.3) id
    GAA11335; Mon, 13 May 2002 06:26:19 -0600 (MDT)
Date: Mon, 13 May 2002 06:26:19 -0600 (MDT)
From: "Nelson H. F. Beebe" <beebe@math.utah.edu>
To: metafont <metafont@ens.fr>
Cc: beebe@math.utah.edu
X-Us-Mail: "Center for Scientific Computing, Department of Mathematics, 110 LCB, University of Utah, 155 S 1400 E RM 233, Salt Lake City, UT 84112-0090, USA"
X-Telephone: +1 801 581 5254
X-Fax: +1 801 585 1640, +1 801 581 4148
X-Url: http://www.math.utah.edu/~beebe
Subject: Re: [metafont] Force (La)TeX to use edited font??
Message-Id: <CMM.0.92.0.1021292778.beebe@plot79.math.utah.edu>
X-Virus-Scanner: AMaVis 0.2.0-pre6 / Virus Scan
X-Loop: metafont@nef.ens.fr
X-Sequence: 550
Precedence: list

Ken Beesley <ken.beesley@xrce.xerox.com> asks about why after
generating a new .mf file, pdftex still used old fonts.

The explanation is quite simple: there is no make-like facility in
this process.  In particular, TeXware does not know about file
dependencies, and makes no attempt to update a dependent file when the
source from which it is derived is newer.  

The one exception to this is that DVI drivers often run MakeTeXPK or
mktexpk to attempt to create a .pk file from some other source (.mf or
.pfa or .pfb), but they do that only when the font cannot be found,
NOT when it is out-of-date with respect to the file from which it is
derived.

In Ken's case, a new .mf file should produce a new .gf file, and then
gftopk should produce a new .pk file, and that should be installed in
some directory in the TEXFONTS path, replacing any older version.

If Ken is working on a system with a make utility, the solution is
straightforward: create Makefile rules that regenerate the .pk file
when the .mf file is changed, and an install target that removes any
existing such system files, and the copies the .pk file into the
system font directory.  Here is an example, which I tested on my
system by making deseret.mf a copy of cmr10.mf; run it the usual GNU
way:

	make all check install

Clean up afterward with

	make clean

------------------------------------------------------------------------
% cat Makefile
FONTDIR = /usr/local/lib/tex/fonts/pk
RM	= /bin/rm -f

all:	deseret.600pk

check:

clean:
	-$(RM) deseret.*gf deseret.*pk deseret.*log deseret.tfm

deseret.600pk:	deseret.600gf
	GFFONTS=. gftopk $?

deseret.600gf:	deseret.mf
	mf "\mode:=ljfour; mag:=1; scrollmode; input deseret"

install:	all uninstall
	cp deseret.600pk $(FONTDIR)/600dpi/
	chmod 664 $(FONTDIR)/600dpi/deseret.600pk
	cp deseret.tfm $(FONTDIR)/tfms/
	chmod 664 $(FONTDIR)/tfms/deseret.tfm

uninstall:
	-$(RM) $(FONTDIR)/*/deseret.*pk $(FONTDIR)/tfms/deseret.tfm
------------------------------------------------------------------------

-------------------------------------------------------------------------------
- Nelson H. F. Beebe                    Tel: +1 801 581 5254                  -
- Center for Scientific Computing       FAX: +1 801 585 1640, +1 801 581 4148 -
- University of Utah                    Internet e-mail: beebe@math.utah.edu  -
- Department of Mathematics, 110 LCB        beebe@acm.org  beebe@computer.org -
- 155 S 1400 E RM 233                       beebe@ieee.org                    -
- Salt Lake City, UT 84112-0090, USA    URL: http://www.math.utah.edu/~beebe  -
-------------------------------------------------------------------------------


From - Mon May 13 17:26:09 2002
Return-Path: <luecking@uark.edu>
Received: from mail.uark.edu (mail.uark.edu [130.184.5.107]) by nef.ens.fr
    (8.10.1/1.01.28121999) with ESMTP id g4DFPuH49467 for <metafont@ens.fr>;
    Mon, 13 May 2002 17:25:56 +0200 (CEST)
Received: from comp.uark.edu ([130.184.5.197]) by mail.uark.edu (Netscape
    Messaging Server 4.15) with ESMTP id GW22V701.W71 for <metafont@ens.fr>;
    Mon, 13 May 2002 10:25:55 -0500
Received: (from luecking@localhost) by comp.uark.edu (8.11.6/8.11.6) id
    g4DFPt315585; Mon, 13 May 2002 10:25:55 -0500 (CDT)
Date: Mon, 13 May 2002 10:25:55 -0500 (CDT)
From: "Daniel Luecking" <luecking@uark.edu>
To: metafont <metafont@ens.fr>
Subject: Re: [metafont] Force (La)TeX to use edited font??
In-Reply-To: <4B919CC6-6647-11D6-9429-000393454058@wanadoo.fr>
Message-Id: <Pine.SOL.4.33.0205131005030.13714-100000@comp.uark.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanner: AMaVis 0.2.0-pre6 / Virus Scan
X-Loop: metafont@nef.ens.fr
X-Sequence: 551
Precedence: list

On Mon, 13 May 2002, Kenneth Beesley wrote:

>
> On Monday, May 13, 2002, at 07:13 , Daniel Luecking wrote:
>
> > store it away. The odd thing is (in MiKTeX at least) it assumes the
> > mf mode "ljfour" (this seems to be compiled in and there is no
> > documented way to change it).
>
> Dear Mr. Luecking,
>
> Many thanks for your reply.  Each installation is different,
> unfortunately,
> and I still don't know what's crucial vs. incidental.  On teTeX, the
> supplied
> modes.mf file includes a mode definition for ljfour and the line
>
> localfont := ljfour ;
>
> I _think_ that this is how ljfour is currently "wired in".  But it's

No. My modes.mf has a different localfont that is recognized by
metafont. What I was talking about is the mode passed to makepk.
Normally, when a driver (like xdvi or dvips) needs a .pk font it calls
makepk (or mktexpk or maketexpk or some similarly named program) and
passes a mf mode. pdftex does the same thing, except there seems to be
no documented way to get it to pass my mode (I do not know if pdftex
sends ljfour or if makepk makes that call). If it is makepk, then on
some systems (not MiKTeX unfortunately) it can be configured.

> I think that my mode is not being ignored.  After producing my new
> fonts, I then 'install'
>       desalph24.1440pk  in  ~/Library/texmf/fonts/pk/desalph/
> and
>      desalph24.tfm  in ~/Library/texmf/fonts/tfm/desalph/
>
> kpsewhich shows that they are indeed being found there.
>

But I think pdflatek may be seeking desalph24.600pk or even
desalph24.72pk. What does your pdftex.cfg say about pk_resolution?
Does there exist a directory ljfour under fonts/pk. with copies of
desalph24.*pk?

> as if pdflatex had generated and cached some other kind of font.  (What
> kind of
> font does pdflatex use?)

It tries to find a scalable font (.pfb or .ttf) and if that fails, it
makes and stores (NOT hidden away, but in a directory like the one I
described) a .pk file AT THE resolution given by pk_resolution, or 72dpi
if no resolution is set.

> I somehow need to tell pdflatex to start all over, re-generating any
> files it needs
> directly from the new desalph24.1440pk and desalph24.tfm.

Chances are it's not even looking for desalph24.1440pk, but it should
find and use the .tfm file. For it to make and use new .pk files, you
have to delete the old ones (not necessarily desalph24.1440pk, but the
ones it actually uses, based on the pk_resolution (as described before).


-- 
Dan Luecking                           Dept. of Mathematical Sciences
luecking@uark.edu                      University of Arkansas
http://comp.uark.edu/~luecking/        Fayetteville, AR 72101


From - Tue May 14 01:31:31 2002
Return-Path: <beesley@wanadoo.fr>
Received: from mel-rto6.wanadoo.fr (smtp-out-6.wanadoo.fr [193.252.19.25])
    by nef.ens.fr (8.10.1/1.01.28121999) with ESMTP id g4DNVNH28637 for
    <metafont@ens.fr>; Tue, 14 May 2002 01:31:23 +0200 (CEST)
Received: from mel-rta10.wanadoo.fr (193.252.19.193) by
    mel-rto6.wanadoo.fr (6.5.007) id 3CDF9D4E000760C9; Tue, 14 May 2002
    01:31:22 +0200
Received: from localhost (80.14.224.50) by mel-rta10.wanadoo.fr (6.5.007)
    id 3CD0C9A700637D62; Tue, 14 May 2002 01:31:22 +0200
Date: Tue, 14 May 2002 01:32:26 +0200
Subject: Re: [metafont] Force (La)TeX to use edited font??
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v481)
From: Kenneth Beesley <beesley@wanadoo.fr>
To: "Daniel Luecking" <luecking@uark.edu>, metafont <metafont@ens.fr>, home <beesley@wanadoo.fr>
Content-Transfer-Encoding: 7bit
In-Reply-To: <Pine.SOL.4.33.0205131005030.13714-100000@comp.uark.edu>
Message-Id: <AEDB7344-66C9-11D6-A3D0-000393454058@wanadoo.fr>
X-Mailer: Apple Mail (2.481)
X-Virus-Scanner: AMaVis 0.2.0-pre6 / Virus Scan
X-Loop: metafont@nef.ens.fr
X-Sequence: 552
Precedence: list


On Monday, May 13, 2002, at 05:25 , Daniel Luecking wrote:

> On Mon, 13 May 2002, Kenneth Beesley wrote:
>
>>
>> On Monday, May 13, 2002, at 07:13 , Daniel Luecking wrote:
>>
>>> store it away. The odd thing is (in MiKTeX at least) it assumes the
>>> mf mode "ljfour" (this seems to be compiled in and there is no
>>> documented way to change it).
>>
>> On teTeX, the
>> supplied
>> modes.mf file includes a mode definition for ljfour and the line
>>
>> localfont := ljfour ;
>>
>> I _think_ that this is how ljfour is currently "wired in".  But it's
>
> No. My modes.mf has a different localfont that is recognized by
> metafont. What I was talking about is the mode passed to makepk.
> Normally, when a driver (like xdvi or dvips) needs a .pk font it calls
> makepk (or mktexpk or maketexpk or some similarly named program) and
> passes a mf mode. pdftex does the same thing, except there seems to be
> no documented way to get it to pass my mode (I do not know if pdftex
> sends ljfour or if makepk makes that call). If it is makepk, then on
> some systems (not MiKTeX unfortunately) it can be configured.

Dear Dr Luecking,

Many thanks for your patience.   You were right, and I'm making
progress again.

>> I think that my mode is not being ignored.  After producing my new
>> fonts, I then 'install'
>>       desalph24.1440pk  in  ~/Library/texmf/fonts/pk/desalph/
>> and
>>      desalph24.tfm  in ~/Library/texmf/fonts/tfm/desalph/
>>
>> kpsewhich shows that they are indeed being found there.
>>
>
> But I think pdflatek may be seeking desalph24.600pk or even
> desalph24.72pk. What does your pdftex.cfg say about pk_resolution?

I can't find a file named pdftex.cfg or pdflatex.cfg in teTeX.  There is 
a texmf.cnf configuration
file, but it doesn't seem to specify a resolution anywhere.  lt does 
include the
following six lines

% Make fonts when unavailable (not all fonts are available for pdf 
directly)
% Useful when using non-pdf-available fonts and going the 
tex->dvi->ps->pdf route
MKTEXPK.pdftex = 1
MKTEXPK.pdflatex = 1
MKTEXPK.pdfetex = 1
MKTEXPK.pdfelatex = 1

Perhaps in teTeX both the mode ljfour and the resolution(s) are wired in.


> Does there exist a directory ljfour under fonts/pk. with copies of
> desalph24.*pk?

Yes.  You're right!   This is the key:

~/Library/texmf/fonts/pk/  now contains two subdirectories
desalph/           which I created myself
and
ljfour/                which got created magically behind my back

desalph/ contains just one pk file, desalph24.1440pk, which I created 
myself
(and which my makefile updates automatically whenever I change and 
recompile my
desalph.mf files).  It reflects the 1440x720 dpi mode that I defined for 
my printer.

ljfour/   contains just one subdirectory  desalph/   which in turn 
contains the
following six pk files:

desalph24.300pk  desalph24.420pk  desalph24.519pk
desalph24.360pk  desalph24.432pk  desalph24.600pk

All these pk files got created behind my back, using (as you wrote)
what appears to be a wired-in ljfour mode.

When I change my .mf files, and update and reinstall the .1440pk and .tfm
files, it's probably these fonts/pk/ljfour/desalph/desalph24.*pk files 
that are not
getting re-generated.

<hack>...</hack>

Yes.  All I have to do, along with modifying and recompiling my .mf 
files, is to delete these
automatically generated pk files, and then they get regenerated 
reflecting my modified font.


>> as if pdflatex had generated and cached some other kind of font.  (What
>> kind of
>> font does pdflatex use?)
>
> It tries to find a scalable font (.pfb or .ttf) and if that fails, it
> makes and stores (NOT hidden away, but in a directory like the one I
> described) a .pk file AT THE resolution given by pk_resolution, or 72dpi
> if no resolution is set.

Well, if not _hidden_, the whole process is a bit obscure and suspicious.

>
>> I somehow need to tell pdflatex to start all over, re-generating any
>> files it needs
>> directly from the new desalph24.1440pk and desalph24.tfm.
>
> Chances are it's not even looking for desalph24.1440pk, but it should
> find and use the .tfm file. For it to make and use new .pk files, you
> have to delete the old ones (not necessarily desalph24.1440pk, but the
> ones it actually uses, based on the pk_resolution (as described before).

Yes.   That's the key.  I just needed to add one line to my makefile.
Thank you so much for your help and your patience.
I'm back in business.

Ken

**************PS********For Future Reference****************

Here are some of the screen messages generated when the pk fonts are 
being
generated automatically:

kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 0+420/600 --dpi 
420 desalph24
mktexpk: Running mf \mode:=ljfour; mag:=0+420/600; nonstopmode; input 
desalph24
This is METAFONT, Version 2.7182 (Web2C 7.3.7)


Font metrics written on desalph24.tfm.
Output written on desalph24.420gf (80 characters, 22564 bytes).
Transcript written on desalph24.log.
mktexpk: 
/Users/beesley/Library/texmf/fonts/pk/ljfour/desalph/desalph24.420pk: 
successfully
generated.
(see the transcript file for additional information) 
</Users/beesley/Library/te
xmf/fonts/pk/ljfour/desalph/desalph24.420pk>kpathsea: Running mktexpk 
--mfmode / --bdpi 600
--mag 1+0/600 --dpi 600 desalph24
mktexpk: Running mf \mode:=ljfour; mag:=1+0/600; nonstopmode; input 
desalph24
This is METAFONT, Version 2.7182 (Web2C 7.3.7)

Font metrics written on desalph24.tfm.
Output written on desalph24.600gf (80 characters, 31552 bytes).
Transcript written on desalph24.log.
mktexpk: 
/Users/beesley/Library/texmf/fonts/pk/ljfour/desalph/desalph24.600pk: 
successfully
generated.
  </Users/beesley/Library/texmf/font
s/pk/ljfour/desalph/desalph24.600pk></usr/local/teTeX/share/texmf/fonts/type1/
b
luesky/cm/cmbx12.pfb></usr/local/teTeX/share/texmf/fonts/type1/bluesky/cm/
cmr12
.pfb></usr/local/teTeX/share/texmf/fonts/type1/bluesky/cm/cmr17.pfb>


From - Wed May 15 01:11:12 2002
Return-Path: <beesley@wanadoo.fr>
Received: from mel-rto3.wanadoo.fr (smtp-out-3.wanadoo.fr
    [193.252.19.233]) by nef.ens.fr (8.10.1/1.01.28121999) with ESMTP id
    g4ENB3H50213 for <metafont@ens.fr>; Wed, 15 May 2002 01:11:03 +0200 (CEST)
Received: from mel-rta9.wanadoo.fr (193.252.19.69) by mel-rto3.wanadoo.fr
    (6.5.007) id 3CDF9C7E00129F3B; Wed, 15 May 2002 01:01:58 +0200
Received: from localhost (80.14.224.119) by mel-rta9.wanadoo.fr (6.5.007)
    id 3CDF7CA4001414E3; Wed, 15 May 2002 01:01:58 +0200
Date: Wed, 15 May 2002 01:03:04 +0200
Subject: Re: [metafont] Force (La)TeX to use edited font??
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Mime-Version: 1.0 (Apple Message framework v481)
From: Kenneth Beesley <beesley@wanadoo.fr>
To: SMuelas <smuelas@mecanica.upm.es>, metafont <metafont@ens.fr>
In-Reply-To: <1021364879.6853.19.camel@simux.mecanica.upm.es>
Message-Id: <BF836298-678E-11D6-B63F-000393454058@wanadoo.fr>
X-Mailer: Apple Mail (2.481)
Content-Transfer-Encoding: 8bit
X-Mime-Autoconverted: from quoted-printable to 8bit by nef.ens.fr id
    g4ENB3H50213
X-Virus-Scanner: AMaVis 0.2.0-pre6 / Virus Scan
X-Loop: metafont@nef.ens.fr
X-Sequence: 553
Precedence: list


On Tuesday, May 14, 2002, at 10:27 , SMuelas wrote:

>> I can't find a file named pdftex.cfg or pdflatex.cfg in teTeX.  There 
>> is
>> a texmf.cnf configuration
>
> Look in
>
> /usr/share/texmf/pdftex/config/pdftex.cnf
>
>
>>

Gracias por su ajuda.  Usted tiene razon.  There is a file (in teTeX)

/usr/local/teTeX/share/texmf/pdftex/config/pdftex.cfg

where I see the line

pk_resolution 600

In the file /usr/local/teTeX/share/texmf.local/dvips/config/config.ps

which I assume is some kind of configuration file for dvips, the mode is
set to 'ljfour', and the line

R 300 600

is commented to state "Also look for this list of resolutions".  In
/usr/local/teTeX/share/texmf.local/xdvi/ I find yet another file, in
yet another format, stating

XDvi*mfMode: ljfour
XDvi*pixelsPerInch: 600
XDvi*shrinkFactor: 8
XDvi*paper: a4
XDvi*wwwBrowser: netscape
XDvi*thorough: true


There seem to be configuration files, in various formats, lurking 
everywhere.

As originally downloaded, the mode for mf font generation was also set as
"ljfour".  I followed the instructions in METAFONT: Guide Pratique to 
localize
that; but it seems like there's a lot more localization that needs to be 
done for
pdftex, dvips, xdvi or whatever other tools are getting used in the 
process.

This is all very forbidding.

Ken



> --
> Santiago Muelas (Depto. de Mecánica)
> http://w3.mecanica.upm.es/~smuelas
> ETSI de Caminos, Canales y Puertos (U.P.M)    smuelas@mecanica.upm.es
> Dr.Aranguren s/n - Ciudad Universitaria       Tf. 91 336 6659
> MADRID 28040
>


From - Wed May 15 09:42:09 2002
Return-Path: <bdesgraupes@easyconnect.fr>
Received: from smarthost1.mail.easynet.fr (smarthost1.mail.easynet.fr
    [212.180.1.68]) by nef.ens.fr (8.10.1/1.01.28121999) with ESMTP id
    g4F7g0H09361 for <metafont@ens.fr>; Wed, 15 May 2002 09:42:00 +0200 (CEST)
Received: from adsl-2-5.adsl.easynet.fr ([212.11.31.5]
    helo=easyconnect.fr) by smarthost1.mail.easynet.fr with esmtp (Exim 3.12
    #1 (Debian)) id 177tQ8-0003gv-00 for <metafont@ens.fr>; Wed,
    15 May 2002 09:42:00 +0200
Message-Id: <3CE210E2.3DAEF396@easyconnect.fr>
Date: Wed, 15 May 2002 09:40:18 +0200
From: Bernard Desgraupes <bdesgraupes@easyconnect.fr>
Reply-To: bdesgraupes@easyconnect.fr
X-Mailer: Mozilla 4.5 [fr] (Macintosh; U; PPC)
X-Accept-Language: fr,pdf
Mime-Version: 1.0
To: metafont <metafont@ens.fr>
Subject: Re: [metafont] Force (La)TeX to use edited font??
References: <BF836298-678E-11D6-B63F-000393454058@wanadoo.fr>
Content-Type: text/plain; charset=us-ascii;
    x-mac-type="54455854";
    x-mac-creator="4D4F5353"
Content-Transfer-Encoding: 7bit
X-Virus-Scanner: AMaVis 0.2.0-pre6 / Virus Scan
X-Loop: metafont@nef.ens.fr
X-Sequence: 554
Precedence: list

> There seem to be configuration files, in various formats, lurking
> everywhere.
>
> As originally downloaded, the mode for mf font generation was also set as
> "ljfour".  I followed the instructions in METAFONT: Guide Pratique to
> localize
> that; but it seems like there's a lot more localization that needs to be
> done for
> pdftex, dvips, xdvi or whatever other tools are getting used in the
> process.
>
>

This is true. Metafont as a standalone program reads the info it needs in modes.mf, Dvips
in config.ps, pdftex in pdftex.cfg and xdvi in xdvi.cfg etc.
With CMacTeX on Mac, dvipreview has a preview.cfg file.
All the locations you mention are correct.
They have different syntaxes, well... they are different programs written by different
authors.

At Metafont level, you are not obliged to use localfont. If you know the mode of your
printer, it is safer (no risk of confusion) to indicate the mode directly on the command
line:
mf \mode = desalpha ; input myfile.mf

Cheers

Bernard


