Paul Johnson wrote:
In Fedora 8 Linux, I'm using the TexLive version of latex that is now
available fore testing. I can ask there about this trouble, but I'm
pretty sure they will send me back here to ask "why does LyX do
that?".
The problem: I get weird output. In a simple document created from
the default everything--with no fancy features-- no preface items
inserted by me, then I have the problem that the xvi and pdf output is
"jumbled". Instead of the default characters, the type font that is
used looks like an old Courier typewriter, but the characters are not
evenly spaced. Some are typed on top of each other, some have extra
spaces between them. I'm attaching this small lyx file to this note,
wondering if anybody sees something funny about it.
Loads fine, output displays fine for me (on both Win XP with MiKTeX and
Ubuntu with TeXLive). I tried both DVI (xdvik on Ubuntu) and PDF
(Evince on Ubuntu), no problems.
I output the lyx document to latex for experimentation, and I cut
lines from the pre-amble until the document came out correct. In all
of the troublesome files, the problem seems to be this one line:
\usepackage[latin9]{inputenc}
What is it? What is latin9?
The problem is all those darned foreigners with their accented
characters and Cyrillic/kanji/whatever symbols. (Note that I'm
including Mac users as foreigners, since the inputenc package supposedly
addresses them as well). When I was younger, everyone used ASCII and
damn well liked it. (Well, there was EBCDIC I suppose.)
Anyway, this just adds in a package to help cope with non-ASCII
characters in the input file (I think). You can find the documentation
for the inputenc style file at
/usr/share/texmf-texlive/doc/latex/base/inputenc.pdf (at least on my
Ubuntu box).
When I run "pdflatex newfile1.tex", I see a lot of messages like this:
pdfTeX warning: pdflatex (file /var/lib/texmf/fonts/map/pdftex/updmap/pdftex.ma
p): ambiguous entry for `ebbx10': font file present but not included, will be t
reated as font file not present
pdfTeX warning: pdflatex (file /var/lib/texmf/fonts/map/pdftex/updmap/pdftex.ma
p): ambiguous entry for `ebmo10': font file present but not included, will be t
reated as font file not present
...
I'm not sure why you're getting any messages about these fonts, since
they don't seem to be used in your document (unless they're set as
defaults in your TeXLive installation??). I have ebbx10 and ebmo10
installed (they're part of the cmbright font package), and they're not
listed (that I can find) in pdftex.map.
Font stuff makes my eyes water at the best of times. Whatever installed
the cmbright fonts should (I think) have updated the font maps to
include them. I can barely make that happen with MiKTeX; I have no idea
how to make it happen with TeXLive (nor why the issue arises in your
document) (nor what it could possibly have to do with the input encoding).
Back tracking, I note no errors in the latex run, but when I view the
dvi file the output looks like hell, and in the terminal I see:
$ xdvi newfile1.dvi
xdvi-xaw3d.bin: Warning: Font map calls for ecrm1200, but it was not
found (will try PK version instead).
xdvi-xaw3d.bin: Warning: Font map calls for ecrm1728, but it was not
found (will try PK version instead).
xdvi-xaw3d.bin: Warning: Font map calls for ecrm1000, but it was not
found (will try PK version instead).
After I delete that preamble line about latin9 input encoding, then
the document processes correctly! Looks great!
What do you think? Where is "latin9" coming from?
It's a default. In LyX, go into Document -> Settings -> Language. You
have the language set as "English" (good choice there, fewer funny
characters) and the options to use the language's default encoding set.
If you uncheck the latter, the Encoding control activates and you can
set LaTeX default, ASCII, utf8 or whatever you like. You might try one
of those and see if your output then looks better, although I don't see
why latin9 should be a problem.
/Paul
