Hi Georg and Kornel,
(I start a new thread to collect all infos about this topic.)
Today I had a closer look and found out that our current test routines
do not test the reality: tex2lyx's aim is to import TeX files to LyX
resulting in compilable LyX files. But this is currently not tested.
For example
- after Jürgen's commit
http://www.lyx.org/trac/changeset/dbe0096c126/lyxgit the test gave me an
error. But in reality I could import all TeX files without problems.
So the test gave me a false positive
- when importing our test file algo2e.tex I get in the LyX console this
warning:
"Ignoring options 'boxed' of package algorithm2e."
This is useful information because indeed, the option "boxed" is removed
by tex2lyx and only added to the document class options. This could lead
to problems in real documents if another loaded package supports an
option with the same name.
So the test result hides a potential problem from us.
- when I import our test file test-modules.tex I get a LyX file that is
uncompilable:
LaTeX Error: Environment lem undefined.
LaTeX Error: \begin{document} ended by \end{lem}.
But the test result tells me that everything is OK with this test file.
So all in all we follow in my opinion the wrong track with our current
test method. Instead we should do it that way:
1. Import the TeX file. If there is any console output this is collected
and output in the test result
2. Export the created LyX file to PDF(pdflatex). If there is any error,
the error messages are output in the test result.
This way we really check if tex2lyx works as expected.
Opinions? (Note that I am technically too limited to set what I proposed.)
regards Uwe
p.s. I added now a few bugs accordingly:
http://www.lyx.org/trac/ticket/9560
http://www.lyx.org/trac/ticket/9561
(more to follow)
