views:

42

answers:

1

On Ubuntu 10.4LTS I'm trying to use the microtype package in a memoir class of document, for example like this:

\usepackage[final,expansion=true]{microtype}

However, when I attempt to compile this (with rubber, latexmk or others) I get an error like this:

job.tex:72: Font csnameendcsname=rm-lmr10+20 at 10.95pt not loadable: Metric (TFM) file not found.

job.tex:72: leading text: \parbox{5in}{Abstract!}

job.tex:72: Font csnameendcsname=rm-lmr10-20 at 10.95pt not loadable: Metric (TFM) file not found.

job.tex:72: leading text: \parbox{5in}{Abstract!}

job.tex:80: Font csnameendcsname=rm-lmr10+20 at 10.0pt not loadable: Metric (TFM) file not found.

job.tex:80: leading text: ...box{11cm}{\noindent{}All rights reserved.}

job.tex:80: Font csnameendcsname=rm-lmr10-20 at 10.0pt not loadable: Metric (TFM) file not found.

job.tex:80: leading text: ...box{11cm}{\noindent{}All rights reserved.}

Note, I'm leaving out lots of code that may be interacting, but the one active line that results in this error is the inclusion of the microtype package.

I'm using \usepackage{lmodern} and \usepackage[T1]{fontenc}, but when I leave those out the problem still exists, and the font names are correspondingly changed from lmr10 to the default cm10.

This code works readily with TeXShop on Mac OS X, however it doesn't seem to work (readily) on Ubuntu. I just don't know enough about how to set up the fonts on Ubuntu to resolve this problem, and I'd be much obliged for input on how to resolve errors such as this.

Thank you.

Brian

+1  A: 

From the microtype manual:

*! Font csnameendcsname=cmr10+20 at 10.0pt not loadable: Metric (TFM) file not found.*

Such an error message could occur if you are trying to employ font expansion
while creating DVI output. Remember, that automatic font expansion only works
when running pdfTEX in PDF mode. Although expansion is also possible in DVI
mode, it requires that all instances of the expanded fonts exist on your TEX
system.

Have you invoked pdftex with pdflatex? If not, what happens when you do?

Charles Stewart
@Charles: Thank you for the helpful reply. `pdflatex` does indeed create the pdf correctly, as you suggest it should. The problem therefore arises because I'm invoking tex via the `mklatex` and `rubber` commands - which evidently create DVI output as part of their tests. I guess my question becomes, then: how can one avoid the creation of DVI output in these build commands?
Brian M. Hunt
@Brian: write your own Makefile?
Charles Stewart
@Charles: Indeed. :)
Brian M. Hunt