LyX correctly gave a warning about mixing InTitle layouts: There was
a LyX note in a Title environment, then there were standard
environments, and then a Title environment. This setup caused
several missing elements in the PDF.
Simply changing the Title environment of the Note to standard solved
the problems: The PDF output is now correct and LyX no longer gives
a warning.
This change fixes the export of our FeynmanDiagrams.lyx example
files on the latest TeX Live 2016.
The IJMP(C|D).lyx examples compiled before the change but might as
well convert these instances of '\rm' also.
The changes were made with the help of the following command:
find ./ -iregex .*lyx -exec sed -i 's/\\rm /\\textrm /g' {} \;
and the resulting diff was confirmed manually.
This commit is consistent with 3cecd4d3.
The difference has been validated with diffpdf.
The following could not be tested and were left unchanged:
AEA.lyx
IJMPC.lyx
ja_beamer-conference-ornate-20min.lyx
The following is the script that I used (in lib/templates):
LYX=../../build/src/lyx
$LYX -E pdf2 $1.old.pdf $1
sed -i "s/^\\\\begin_inset Separator parbreak$/\\\\begin_inset Separator plain/" $1
sed -i "/^\\\\begin_inset Separator latexpar$/ { N; d; }" $1
$LYX -e lyx $1
$LYX -E pdf2 $1.pdf $1
diffpdf $1.old.pdf $1.pdf
Some templates had the inputenc setting "default" (meaning
use the language default encoding, (not TeX's default which is 7-bit ASCII) but
don't load inputenc, leave handling of non-ASCII characters to the author).
This is no apparent problem as long as no non-ASCII character is used in the
document. It is very unsave, however, as any non-ASCII character used in the
document has the potential to either make compilation fail or be
misrepresented in the output.
Also MacOSX ReadMe files. Note that a few lib/doc files are
also "updated" because trailing spaces are removed, but their file
formats are the same because they were recently updated at 83672113.
I did "git checkout LFUNs.lyx" because this file is generated
automatically and has a special header.
This template was only reported as failing to compile by LyX as of
0a6120cb. I do not know how long this template was actually failing
to compile without error. The problem was that the class requires
\doi to be defined. This might not have been a requirement in
previous versions of the class.
Thanks to Enrico for finding the problem and solution.
Compilation was failing with TeX Live 2013 because of
the format of one of the references. This commit just
changes one of the references to a different one.
- this brings back all our template files (they are no example files, would have been a regression otherwise because LyX 2.0 offers them already in "new from template")
- the thesis files will stay in the examples folder for now until we have a real fiix for bug #8643
Exporting this outdated document currently hangs on some systems.
Further, there is no natural link between AGU and DocBook
and this could be confusing to a user who is looking for
the AGU template.
Manuals, examples and templates that use (traditional) bibtex should have set the bibliography processor to bibtex. Else, these documents do not compile if a user has set the processor to 'biber' in the preferences
This provides a working examples that can be viewed directly
and makes the templates compilable out-of-the box.
When moving the example, I removed what I interpreted to be
an errant apostrophe.
This document does not export to PDF. Further, if one tries
to export to PDF on some systems, the process hangs. This commit
thus changes the default output format to xhtml and explains in a
note at the top that LyX does not currently support exporting this
document to PDF.
Note also that this document seems to be outdated and so is a
candidate for attic.
Further, this document is a candidate for being renamed. Currently
users might be confused if they are looking for the canonical way
(no need for DocBook) to write an article for AGU journals. For
that, they should use AGUTeX.lyx.
The labels for the references are now in the format
"author(year)". Without this, the following error is given:
"Bibliography not compatible with author-year citations"
Thanks to Richard for the fix.
When a user creates a new document from a template, the template
is copied but relative paths are not changed, so the resulting
.lyx file is broken. By moving documents with relative paths to
examples, the files will compile out of the box.
A long-term solution that allows for relative paths in templates
is still desired and will be discussed in #8643 or in a new ticket.
With LyX configured in this way, the user would only need to:
File > New from Template > EPS.lyx (or PDF-cropped.lyx):
- insert a math inset and type in an equation, or create whatever
content LaTeX can handle,
- view/export to cropped EPS/PDF.
This would allow for LyX to act as a "generator for includable graphics" (equations, commented graphics, etc).
This fixes bug #7839.
- mention that the aa class loads natbib to avoid compilation errors
- the aa package contains an outdated an customized version of natbib.sty. This file only works with aa, but breaks the compilation of many other files on your system, therefore remove the bibliography and replace it by BibTeX
- add a note about the encoding
- make template compilable
- update it according to the latest AEA guidelines
- add 4 missing styles to the layout:
* \keywords
* \JEL
* figurenotes environment
* tablenotes environment
Before, only PDFs were being generated so latex did not compile.
Now, both PDF and EPS files are generated.
This is not efficient but could save the user some pain, which is
the goal of templates.
An alternative would be to set the default output to use pdflatex.
The layout now takes care of \begin{article} and \end{article}
by using \AtBeginDocument and \AtEndDocument.
This cleans up the template a little by removing some ERT. The
user no longer needs to read the two notes explaining why the
ERT boxes were necessary. The user also does not need to think
about why this LaTeX environment exists.
The reasons are specified in the note at the top of the template:
It is possible to export with plain LaTeX but an option must be
specified to remove some elements (e.g. JSS logo).
