>>>>> "Thomas" == Thomas Esser <[EMAIL PROTECTED]> writes:
> As other have guessed: I don't like that europs approach as the
> type1 files cannot be distributed with teTeX.
On the other hand there is support for Y&Y's Lucida fonts which are
not free as well.
I'm not sure whether it is the most user friendly way to provide the
support files along with teTeX, it is probably quite convenient for
people who have the Lucida fonts already installed.
Installing the 'real' fonts shouldn't be difficult, but it might be a
bit inconvenient. You have to find out what you need, find out where
it is on the disk, where the files should go, create the appropriate
directories and, because the Y&Y stuff is based on WinDOS, you have to
keep in mind that file names are case sensitive under UNIX.
Actually, it is relatively easy, sine teTeX includes everything but the font
files themselves --- and instructions are provided with the
"Unix" version of the fonts. (see attached for generic instructions for TeTeX).
By the way, there should be no name case issue with LucidaBright --- that problem
related to MathTime, and was *not* caused by the font originators. Spivak used
upper case names for the actual font file names, and Y&Y kept that convention.
Later, when distribution of standard LaTeX was considered, the CD-ROM file
system suitable for Unix did not support case for file names, so everything
had to be the same case (so don't blame everything on Windows :-).
At that time several files in the standard distribution were renamed and
Y&Y was asked to consider renaming the metric files for MathTime,
which they did. Unfortunately in the TeX world old files resurface periodically
and sometimes multiply faster than new ones. So now there is a mix of
files lying around some using lower case and some upper case for the
file names mtmi, mtsy, mtex etc. (Note that the PS FontNames themselves
*are* always upper case, and that the reference names in LaTeX are also---
we are only talking here about the actual file names, such as TFMs and PFBs).
You may wonder why Spivak chose upper case file names in the first case.
You can blame this one on the Macintosh (again, not Windows :-) which used
a font file name abbreviation scheme that would have mapped many
long CM font names into the same abbreviation --- Barry Smith solved
this problems by making CM font file names all upper case. Spivak
saw this and assumed that font file names needed to be upper case.
>From the viewpoint of a user things could be much more convenient:
Imagine a tar.gz file containing all the support files along with the
*real* fonts that can be extracted in any texmf* directory. And this
tar.gz file should, of course, be distributed by Y&Y.
Well, that is an interesting idea. Of course it brings with it issues of just
how many font users would benefit from this. Since Unix has no system
level support for scalable fonts (or, on systems that do, such as Solaris,
or NeXT, or Mac OS X, it is unique to that system), it is impossible to
provide anything generic. Also, while there is always much complaining,
noone who has the fonts ever offered to just make up such as tar file and
email it to Y&Y for their consideration.
Finally, keep in mind that sales of license for fonts for use with TeX are
virtually non-existent, and that the "maintainence" (which, of course, has
nothing to do with fonts, which are fixed, and has everything to do with
developments in the OS, ATM, TeX system worlds) outweighs income,
at least in the Macintosh and Unix worlds.
I suppose that you want to leave the Lucida support files in teTeX
because there are some people using them. But if you ever decide to
remove them in the future because the fonts are not free, I strictly
recommend to put them to CTAN.
Same would apply to MathTime etc. Keep in mind that the *metric* files
are of course "free". Even for fonts from major foundries like Adobe.
----------------------------------------------------------------------------
Microsoft isn't the answer. Microsoft is the question, and the answer is NO.
----------------------------------------------------------------------------
Of course, you are not biased in any way :-)
Statistically, most of the "complaints" about font files come from people
who would never consider paying a license for a font :-)
Berthold K.P. Horn mailto:[EMAIL PROTECTED] http://www.ai.mit.edu/people/bkph (BK)
=======================================================================
Installing PS Type 1 fonts for use with teTeX (file tetexfnt.txt)
=======================================================================
Copyright (C) 1998, 1999, 2000, 2001 Y&Y, Inc. All Rights Reserved
In teTeX 1.0 (and later), font support (.sty, .fd, .tfm files etc.)
is already all set up for you. You just need to put the actual
font files (in .pfa or .pfb format) into localtexmf/fonts/type1
(or texmf/fonts/type1 if you have to) --- and it will work!
IMPORTANT: You have to run 'texhash' after making changes to make
sure that the systems file directory cache is updated.
OR: Alternatively run mktexlsr.
If some system component has trouble finding files, then try
kpsewhich which shows where searches go to - Or turn on the
debugging options in DVIPS.
NOTE: You should create a 'localtexmf' directory tree ---
if you do not alredy have one --- rather than modifying the
files in the 'texmf' tree. You then advise teTeX of your
local tree in /usr/lib/teTeX/texmf.cnf
As for teTeX releases, visit the teTeX homepage at
http://tug.org/teTeX/ Note that teTeX is generated by:
Thomas Esser http://www-b.informatik.uni-hannover.de/~te/
University of Hannover, Germany
Informatics Institute (Databases and Information Systems Group)
The current version of teTeX may be found on CTAN (or at
ftp://ftp.rrzn.uni-hannover.de/pub/local/misc/teTeX-beta/)
There is a teTeX-specific mailing list:
[EMAIL PROTECTED]
========================================================================
If you are *not* using the latest version of teTeX (but why?), read on:
========================================================================
(0) Before you start creating directories and copying files,
select a font encoding (character layout) for *text* fonts.
We recommend TeX 'n ANSI, referred to as LY1 when using
the LaTeX PSNFSS package. See /psnfss/ly1.txt on the diskette.
Alternative encodings include Cork encoding (referred to as T1),
and `raw 8bit' encoding (8r). We do *not* recommend the old
`TeX text' (OT1) encoding used by Computer Modern fonts, nor Adobe
StandardEncoding (ASE), since these have sparse glyph coverage. See
also http://www.YandY.com/ly1.htm and http://www.YandY.com/usely1.htm.
The encoding you select will determine which text font TFMs to
use (step 3 below), how DVIPS reencodes the text fonts (step 6),
and what you tell LaTeX about text font encoding (step 9).
Note that *text* font encoding does not affect *math* fonts.
(1) Create a directory for the actual outline fonts in PFA (or PFB) format,
e.g. /texmf/fonts/type1/yandy. Copy the PFA (or PFB) files from the
top level directory on the diskette to that directory.
(2) Create a directory for the math (i.e. non-text) TeX font metric (TFM)
files, e.g. /texmf/fonts/tfm/yandy. Copy the math font TFM files
from the TFM directory on the diskette to this directory.
(3) If there are also text fonts, create a directory for the corresponding
TFM files. It is recommended that this be given a name that is related
to the chosen text font encoding to avoid confusion later. For example,
for TeX 'n ANSI (LY1) encoding, create /texmf/fonts/tfm/yandy/texnansi.
For Cork (T1) use the name 'tex256', for Adobe StandardEncoding (ASE)
use 'standard', for `TeX text' (OT1) use 'textext'. The names correspond
to TFM file sub-directories on the diskette. Copy the TFM files from
the appropriate sub-directory. For TeX 'n ANSI e.g. copy TFM files
from /tfm/texnansi on the diskette to /texmf/fonts/tfm/yandy/texnansi.
(4) In the case of the MathTime 1.1 and MathTime Plus fonts there are also
a few virtual font (VF) files in the VF directory on the diskette.
Create a directory for these, e.g. /texmf/fonts/vf/yandy. Copy the
virtual font files (e.g. mtmi.vf) from the diskette to this directory.
(5) Copy the font encoding files in PS form for DVIPS from the enc directory
on the diskette to /texmf/dvips/base. This includes texnansi.enc for LY1,
tex256.enc for T1, and 8r.enc for `8bit raw' encoding (base for T1 and OT1).
(6) Select a suitable psfonts.* file from the psfonts directory on the
diskette (see readme.txt in that directory). Copy this file to
/texmf/fontname. Add a line starting with p+ to config.ps in
/texmf/dvips/config to refer to this file. For example, when
using the MathTime fonts with text fonts in LY1 encoding, copy
psfonts.mty, and add the line `p+ psfonts.mty' to config.ps
(7) Copy the files from the PSNFSS directory on the diskette to
/texmf/tex/latex/psnfss (unless you already have more recent
versions of those files there from CTAN). This may include
various *.dtx, *.ins, *.yy, *.fdd, *.sty and *.fd files.
(8a) In the case of MathTime, read mathtime.txt and then run TeX on
mathtime.ins in the PSNFSS directory to create mathtime.sty (and
other files such as *.fd ) from mathtime.dtx and mathtime.fdd.
Then run LaTeX on mathtime.dtx and print the resulting documentation.
(8b) In the case of LucidaBright + LucidaNewMath, read lucidabr.txt and run
Tex on lucidabr.yy in the PSNFSS directory to create lucidabr.sty
(and other files) from lucidabr.dtx. (You can instead run TeX on
lucidabr.ins if you want to refer to the fonts by their `Karl Berry'
names). Then run LaTeX on lucidabr.dtx and print the resulting
documentation.
(9) In LaTeX 2e, make sure to specify the text font encoding you are using.
For TeX 'n ANSI, add \usepackage[LY1]{fontenc} between the
\documentclass{...} and the \begin{document}. For Cork encoding
add \usepackage[T1]{fontenc} instead.
(10) Tell LaTeX 2e which fonts you want to use, e.g. \usepackage[LY1]{lucidabr}
or \usepackage[LY1,mtbold]{mathtime}. This goes *after* the encoding
selecting specified above. Note that the LucidaBright and MathTime
packages both take a plethora of options! Please check `mtoption.txt'
or `lboption.txt' respectively in the `txt' directory on the diskette.
(11) In the case of MathTime, you may also need to specify what fonts to use
for text. You can e.g. add \usepackage{times} for this purpose.
Examples use in LaTeX 2e:
\usepackage[LY1]{fontenc} % specify text font encoding
\usepackage[LY1]{lucidabr} % switch text and math fonts (LucidaBright)
\usepackage[LY1]{fontenc} % specify text font encoding
\usepackage[LY1,mtbold]{mathtime} % switch math fonts (MathTime)
\usepackage{times} % switch text fonts (Times-Roman)
(12) If you use some utility like PStoPK, then also copy the AFM files.
Copy the AFM files from the top level directory on the diskette to
/texmf/fonts/type/afm/yandy.
These files are also used by Display PostScript, by the way.
(13) You have to run 'texhash' after making changes to make sure that
the systems file directory cache is updated.
Things to look out for:
-----------------------
(1) Look out for pre-existing style and font definition files in the
'texmf' tree that may be "shadowing" files you place in your
'localtxmf' tree. This applies particularly to LucidaBright,
where the files in the PSNFSS package may have been generated by
expanding lucidbr.ins instead of lucidabr.yy
(2) Look our for pre-existing psfonts.map files for DVIPS that may
be set up to either not reencode the text fonts or reencode them
to something other than you want. Again such files may shadow
the "p+ ..." additions you make to config.ps
A historical note:
------------------
Originally, the MathTime font files had uppercase names (e.g. MTMI.tfm).
This created a lot of interplatform portability problems. The files
now are all lowercase. This can be a problem if you have an older version
of the PSNFSS support files for MathTime. Use the ones from the diskette.
Note that the PostScript FontNames still are upper case, but this does not
affect the font *file* names, or the TFM names used by TeX.
When LaTeX 2e was first released, the names of font definition files had
mixed case (e.g. LY1enc.def). This lead to problems when dumping CTAN on
CD-ROM in ISO 9660 format. These files now have all lower case names.
Some files may not be found by TeX if you have an older PSNFSS installation.
Note also that if you read diskettes on Unix using MTOOLS then files may
appear with all uppercase names.
Highly optional:
---------------
(1) In the case of MathTime, there may be Metafont (MF) files that can be used
to create bitmapped PK font files that are crude approximations of the
real thing. Copy the MF files from the mf directory on the diskette to
/texmf/fonts/source/yandy. Note that it is normally better to use PStoPK
to create bitmapped fonts for XDVI than to use these MF files.
(2) In the case of MathTime, there may be bitmapped PK font files in the PK
directory on the diskette. You could copy these to /texmf/fonts/pk/yandy
although you probably would need to rename them to a different PK font
file naming convention. It is normally better to use PStoPK to create
bitmapped fonts for XDVI than to use these PK files.
(3) There are two utilites for converting between PFA and PFB font file format.
You could copy these from the prog directory on the diskette to some
sub-directory of /bin on your system. You typically wont need these,
and probably already have a utility called pfb2pfa.
References: You will find a detailed discussion of the Unix/DVIPS/VF/PS/fontinst
approach to using PS Type 1 fonts in Chapter 10 of the
`LaTeX Graphics Companion' by Michel Goossens, Sebastian Rahtz,
and Frank Mittelbach, published by Addison-Wesley ISBN 0-201-85469-4.
Basic information on LaTeX 2e PSNFSS font handling may be found
in Chapter 7 of
`The LaTeX Companion' by Michel Goossens, Frank Mittelbach, and Alexander
Samarin published by Addison-Wesley ISBN 0-201-54199-8.
See also
`TeX Unbound' by Alan Hoenig, Oxford University Press,
ISBN 0-19-509686-X or ISBN 0-19-509685-1
************************************************************************
Y&Y, Inc., 106 Indian Hill, Carlisle, MA 01741, USA
(800) 742-4059 (from North America only)
(978) 371-3286 (voice) (978) 371-2004 (fax)
mailto:[EMAIL PROTECTED] http://www.YandY.com
************************************************************************
