Tag Info

New answers tagged

1

In my case, it was caused by a Greek symbol pasted directly into body text instead of inside an inline equation. My Lyx file was working fine until I did something and this error showed up, pointing at an equation that had been showing up just fine previously. I discovered that the problem was in fact that I had typed a Greek symbol in standard text (not ...


2

When you do \usepackage[<ENCODING>]{fontenc} the file <encoding>enc.def is loaded (the encoding name is converted to lowercase for reasons due to uniformity in the various file systems). For instance \usepackage[T1]{fontenc} will load t1enc.def. The start of this file is \ProvidesFile{t1enc.def} [2005/09/27 v1.99g Standard LaTeX ...


6

There should never be any of |<>" in text input whatever the encoding so the problem should not arise. Perhaps the simplest test would be to add \showoutput then search or \OT1.* > for example \documentclass{article} \showoutput \begin{document} <a> \end{document} Then the lines ....\OT1/cmr/m/n/10 < ....\OT1/cmr/m/n/10 > In ...


11

An NFSS question ... how nice :-) Looks like a quarter of century old deficiency. One could argue whether or not this is a bug or whether it is really due to the fact that in the preamble typesetting is not quite supported — I guess in the end it is a bit of both as NFSS sets up its final tables only at begin document. However, I tried to accommodate for ...


1

There is a possibility to compile your document directly to a pdf. The compiler is called pdflatex. There you need the package epstopdf which has to come after the package graphicx for correct compilation of your eps graphics. You have to hand over to the compiler the statement pdflatex --shell-escape. Maybe you need also to add --enable-write18. MWE: ...



Top 50 recent answers are included