I'm trying to use this Garamond package to use its Garamond font, and I can't use it if I try to tidy the files into their own subdirectory.
Contrary to the instructions, if I unpack the zip in the same directory as my document (giving me a package
directory with many .tfm and other files) and add package
to my TEXINPUTS path, compiling fails with:
[1] (input/package/t1ggm.fd)
kpathsea: Running mktextfm ggmr8t
mktextfm: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input ggmr8t
This is METAFONT, Version 2.718281 (TeX Live 2012/Debian)
kpathsea: Running mktexmf ggmr8t
! I can't find file `ggmr8t'.
<*> ...:=ljfour; mag:=1; nonstopmode; input ggmr8t
Please type another input file name
! Emergency stop.
<*> ...:=ljfour; mag:=1; nonstopmode; input ggmr8t
Transcript written on mfput.log.
grep: ggmr8t.log: No such file or directory
mktextfm: `mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input ggmr8t' failed to make ggmr8t.tfm.
kpathsea: Appending font creation commands to missfont.log.
! Font T1/ggm/m/n/7=ggmr8t at 7.0pt not loadable: Metric (TFM) file not found.
<to be read again>
relax
l.72 \garamond
?
However, if I extract all of the files from the package
directory into the same directory as my document, it compiles fine and my text is in Garamond as desired.
I'd really prefer to keep all these files in a subdirectory, whether that's named package
or (preferably) garamond
. Is there some extra environment variable to set for the tfm files, so it doesn't try to compile them again from scratch?
tfm
and other font-related files. in addition, i note that the garamond package you got "correctly" usesugm
for the font id, but all your error message refer toggm
. have you hacked the package somehow? if so, how? – wasteofspace Dec 10 '12 at 17:19packages
or moved them up one directory. I have no idea what's up withugm
vsggm
, I literally unzipped it, add\usepackage{garamond}
and\garamond
and it works or doesn't based on file location. I'm using whatever distribution of TeX comes with Ubuntu 12.10, looks like TeX Live 2012.20120611-4. (If there's a command I can run for more useful info, please let me know). As for TEXINPUTS, that's due to some hassle I posted another question about. – pushcx Dec 10 '12 at 17:36