Re: what is this: \usepackage[latin9]{inputenc} and why does TexLive hate it?
Paul A. Rubin wrote: 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.) We 'darned' always extended ASCII in various ways, because it was always insufficient. For a clear idea of the problem: Try removing three vowels from ASCII, and then try writing anything serious at all. You can't. :-) More or less cumbersome workarounds have been in use since they started replacing mechanical typewriters with word processing. Because you can't write a decent business letter with just ascii. Now, UTF-8 will probably put an end to the mess for good. Helge Hafting
Re: what is this: \usepackage[latin9]{inputenc} and why does TexLive hate it?
Paul A. Rubin wrote: 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.) We 'darned' always extended ASCII in various ways, because it was always insufficient. For a clear idea of the problem: Try removing three vowels from ASCII, and then try writing anything serious at all. You can't. :-) More or less cumbersome workarounds have been in use since they started replacing mechanical typewriters with word processing. Because you can't write a decent business letter with just ascii. Now, UTF-8 will probably put an end to the mess for good. Helge Hafting
Re: what is this: \usepackage[latin9]{inputenc} and why does TexLive hate it?
Paul A. Rubin wrote: 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.) We 'darned' always extended ASCII in various ways, because it was always insufficient. For a clear idea of the problem: Try removing three vowels from ASCII, and then try writing anything serious at all. You can't. :-) More or less cumbersome workarounds have been in use since they started replacing mechanical typewriters with word processing. Because you can't write a decent business letter with just ascii. Now, UTF-8 will probably put an end to the mess for good. Helge Hafting
what is this: \usepackage[latin9]{inputenc} and why does TexLive hate it?
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.
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?
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
...
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?
--
Paul E. Johnson
Professor, Political Science
1541 Lilac Lane, Room 504
University of Kansas
newfile1.lyx
Description: application/lyx
Re: what is this: \usepackage[latin9]{inputenc} and why does TexLive hate it?
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
Re: what is this: \usepackage[latin9]{inputenc} and why does TexLive hate it?
On Mon, Jan 21, 2008, Paul A. Rubin wrote: The problem is all those darned foreigners with their accented characters and Cyrillic/kanji/whatever symbols In LyX, go into Document - Settings - Language. You have the language set as English (good choice there, fewer funny characters) Well, you do get fewer funny characters, but only monarchists should follow your choice. Red-blooded patriots who support Big Ten football should choose American as their document language. :-) dave case (MSU, class of 1970)
Re: what is this: \usepackage[latin9]{inputenc} and why does TexLive hate it?
David A. Case wrote: On Mon, Jan 21, 2008, Paul A. Rubin wrote: The problem is all those darned foreigners with their accented characters and Cyrillic/kanji/whatever symbols In LyX, go into Document - Settings - Language. You have the language set as English (good choice there, fewer funny characters) Well, you do get fewer funny characters, but only monarchists should follow your choice. Red-blooded patriots who support Big Ten football should choose American as their document language. :-) dave case (MSU, class of 1970) Good point -- although that might risk disenfranchising da Youpers. I'm not sure what (if any) character set they have, and many of them are Big 10 fans. :-) /Paul
what is this: \usepackage[latin9]{inputenc} and why does TexLive hate it?
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.
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?
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
...
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?
--
Paul E. Johnson
Professor, Political Science
1541 Lilac Lane, Room 504
University of Kansas
newfile1.lyx
Description: application/lyx
Re: what is this: \usepackage[latin9]{inputenc} and why does TexLive hate it?
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
Re: what is this: \usepackage[latin9]{inputenc} and why does TexLive hate it?
On Mon, Jan 21, 2008, Paul A. Rubin wrote: The problem is all those darned foreigners with their accented characters and Cyrillic/kanji/whatever symbols In LyX, go into Document - Settings - Language. You have the language set as English (good choice there, fewer funny characters) Well, you do get fewer funny characters, but only monarchists should follow your choice. Red-blooded patriots who support Big Ten football should choose American as their document language. :-) dave case (MSU, class of 1970)
Re: what is this: \usepackage[latin9]{inputenc} and why does TexLive hate it?
David A. Case wrote: On Mon, Jan 21, 2008, Paul A. Rubin wrote: The problem is all those darned foreigners with their accented characters and Cyrillic/kanji/whatever symbols In LyX, go into Document - Settings - Language. You have the language set as English (good choice there, fewer funny characters) Well, you do get fewer funny characters, but only monarchists should follow your choice. Red-blooded patriots who support Big Ten football should choose American as their document language. :-) dave case (MSU, class of 1970) Good point -- although that might risk disenfranchising da Youpers. I'm not sure what (if any) character set they have, and many of them are Big 10 fans. :-) /Paul
what is this: \usepackage[latin9]{inputenc} and why does TexLive hate it?
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.
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?
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
...
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?
--
Paul E. Johnson
Professor, Political Science
1541 Lilac Lane, Room 504
University of Kansas
newfile1.lyx
Description: application/lyx
Re: what is this: \usepackage[latin9]{inputenc} and why does TexLive hate it?
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
Re: what is this: \usepackage[latin9]{inputenc} and why does TexLive hate it?
On Mon, Jan 21, 2008, Paul A. Rubin wrote: > > The problem is all those darned foreigners with their accented > characters and Cyrillic/kanji/whatever symbols > > In LyX, go into Document -> Settings -> Language. You > have the language set as "English" (good choice there, fewer funny > characters) Well, you do get fewer funny characters, but only monarchists should follow your choice. Red-blooded patriots who support Big Ten football should choose "American" as their document language. :-) dave case (MSU, class of 1970)
Re: what is this: \usepackage[latin9]{inputenc} and why does TexLive hate it?
David A. Case wrote: On Mon, Jan 21, 2008, Paul A. Rubin wrote: The problem is all those darned foreigners with their accented characters and Cyrillic/kanji/whatever symbols In LyX, go into Document -> Settings -> Language. You have the language set as "English" (good choice there, fewer funny characters) Well, you do get fewer funny characters, but only monarchists should follow your choice. Red-blooded patriots who support Big Ten football should choose "American" as their document language. :-) dave case (MSU, class of 1970) Good point -- although that might risk disenfranchising da Youpers. I'm not sure what (if any) character set they have, and many of them are Big 10 fans. :-) /Paul
