As most of us agreed that eLyXer should be integrated, the following needs to
be done:
1. the license of eLyXer need to be uniform with LyX's license (GPL v2 not v3)
2. eLyXer should get a more explicit name like lyx2html
3. we need to find a suitable location, under
lib/scripts/lyx2html
or
lib/lyx2html
or
lib/lyx2lyx/lyx2html
4. we need two HTML output formats to distinguich between tex4ht and eLyXer -> I have implemented
this now as "html2"
I think that's it.
Concerning the current status of eLyXer, it is much better than tex4ht in the test I made as it can
process nearly every file I have while tex4ht silently dies with 50% of my documents, especially
with the LyX manuals. eLyXer is of course not yet complete, but that's the same as for tex2lyx. An
integration to LyX assures that everybody can make it better and fix bugs. And only this way we can
assure that it will work correctly with lyx2lyx. We still have some time until LyX 2.0svn is ready,
so I think we should do the inclusion now.
Even if eLyXer (lyx2html) might not be ready for LyX 2.0 we can disable it by commenting out 2 lines
in configure.py.
regards Uwe
p.s. Alex, with eLyXer 0.17 I get this error (I just upgraded to Python 2.6.2):
Traceback (most recent call last):
File "D:/LyXSVN/lyx-devel/build-msvc/bin/../Resources/scripts/eLyXer/elyxer.py
", line 28, in <module>
from util.trace import Trace
ImportError: No module named util.trace
