Re: cls file problem, error previewing format
Is what you posted the entire LaTeX log file? Usually the first step is to find the first error message in the log file and try to track down the reason for it. Frequently (but not always) you can find a specific source; it's then a matter of whether that is user error in the document, a discrepancy between the LyX layout file and the document class file, an encoding error, or a gremlin infestation. When the origin of the error message is imprecise, a bisection search (cut out and restore parts of the document until you pin down a fairly small portion whose excision removes the error) frequently helps. If the log file, as viewed from LyX, contains no error message, I'd try exporting the document to a .tex file (LaTeX (pdflatex) export format) and applying pdflatex to it manually, in hopes of seeing the error message. If the document compiles without error, then of course try to view the PDF file (which may yield an error message from the viewer, or perhaps the operating system). Paul
Re: cls file problem, error previewing format
Is what you posted the entire LaTeX log file? Usually the first step is to find the first error message in the log file and try to track down the reason for it. Frequently (but not always) you can find a specific source; it's then a matter of whether that is user error in the document, a discrepancy between the LyX layout file and the document class file, an encoding error, or a gremlin infestation. When the origin of the error message is imprecise, a bisection search (cut out and restore parts of the document until you pin down a fairly small portion whose excision removes the error) frequently helps. If the log file, as viewed from LyX, contains no error message, I'd try exporting the document to a .tex file (LaTeX (pdflatex) export format) and applying pdflatex to it manually, in hopes of seeing the error message. If the document compiles without error, then of course try to view the PDF file (which may yield an error message from the viewer, or perhaps the operating system). Paul
Re: cls file problem, error previewing format
Is what you posted the entire LaTeX log file? Usually the first step is to find the first error message in the log file and try to track down the reason for it. Frequently (but not always) you can find a specific source; it's then a matter of whether that is user error in the document, a discrepancy between the LyX layout file and the document class file, an encoding error, or a gremlin infestation. When the origin of the error message is imprecise, a bisection search (cut out and restore parts of the document until you pin down a fairly small portion whose excision removes the error) frequently helps. If the log file, as viewed from LyX, contains no error message, I'd try exporting the document to a .tex file (LaTeX (pdflatex) export format) and applying pdflatex to it manually, in hopes of seeing the error message. If the document compiles without error, then of course try to view the PDF file (which may yield an error message from the viewer, or perhaps the operating system). Paul
cls file problem, error previewing format
I've tried to install a new document class, using latex macro files supplied by a journal called Bayesian Analysis. I'm not sure they work right, my installation of Lyx 2.0 RC1 on ubuntu 64 linux seems to work ok for other formats. When I try to use this document class I get an error such as 16:14:48.221: Previewing ... 16:14:48.233: (buffer-view: Ctrl+R) 16:14:48.236: pdflatex batry.tex 16:14:48.252: This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian) 16:14:48.253: restricted \write18 enabled. 16:14:48.255: entering extended mode 16:14:48.255: (./batry.tex 16:14:48.256: LaTeX2e 2009/09/24 16:14:48.256: Babel v3.8l and hyphenation patterns for english, usenglishmax, dumylang, noh 16:14:48.256: yphenation, ukenglish, loaded. 16:14:48.257: 16:14:48.292: Error while previewing format: pdf2 16:18:46.568: Automatic save done. Could anyone give me some clues as to the best way to debug this and find the problem? Thanks Jim === Dr. Jim Maas University of East Anglia
cls file problem, error previewing format
I've tried to install a new document class, using latex macro files supplied by a journal called Bayesian Analysis. I'm not sure they work right, my installation of Lyx 2.0 RC1 on ubuntu 64 linux seems to work ok for other formats. When I try to use this document class I get an error such as 16:14:48.221: Previewing ... 16:14:48.233: (buffer-view: Ctrl+R) 16:14:48.236: pdflatex batry.tex 16:14:48.252: This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian) 16:14:48.253: restricted \write18 enabled. 16:14:48.255: entering extended mode 16:14:48.255: (./batry.tex 16:14:48.256: LaTeX2e 2009/09/24 16:14:48.256: Babel v3.8l and hyphenation patterns for english, usenglishmax, dumylang, noh 16:14:48.256: yphenation, ukenglish, loaded. 16:14:48.257: 16:14:48.292: Error while previewing format: pdf2 16:18:46.568: Automatic save done. Could anyone give me some clues as to the best way to debug this and find the problem? Thanks Jim === Dr. Jim Maas University of East Anglia
cls file problem, error previewing format
I've tried to install a new document class, using latex macro files supplied by a journal called "Bayesian Analysis". I'm not sure they work right, my installation of Lyx 2.0 RC1 on ubuntu 64 linux seems to work ok for other formats. When I try to use this document class I get an error such as 16:14:48.221: Previewing ... 16:14:48.233: (buffer-view: Ctrl+R) 16:14:48.236: pdflatex "batry.tex" 16:14:48.252: This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian) 16:14:48.253: restricted \write18 enabled. 16:14:48.255: entering extended mode 16:14:48.255: (./batry.tex 16:14:48.256: LaTeX2e <2009/09/24> 16:14:48.256: Babel and hyphenation patterns for english, usenglishmax, dumylang, noh 16:14:48.256: yphenation, ukenglish, loaded. 16:14:48.257: 16:14:48.292: Error while previewing format: pdf2 16:18:46.568: Automatic save done. Could anyone give me some clues as to the best way to debug this and find the problem? Thanks Jim === Dr. Jim Maas University of East Anglia
