Abdelrazak Younes wrote:
Alex Fernandez wrote:
Question 1: do you use the lyx2lyx framework? The advantage would be
that
lyx2lyx knows about the lyx format of all revisions.
Nope, and it is a very good idea. However I would like to build a
standalone tool that does not require other libraries to work, i.e. to
minimize dependencies -- not because users will not have lyx2lyx
installed but because of runtime problems.
I am not sure I follow you, why would you have runtime problems if
lyx2lyx is installed? In case that was not clear, lyx2lyx is pure
python, just as your eLyXer. Or are you talking about the python
modules that lyx2lyx requires?
I am afraid that locking you tool to a specific lyx format is not a
good long term option.
Yes, I had the same worry. The LyX file format is so unstable, and the
tool would have to be updated every time it changed, i.e., every time we
release a new version. And what about if we actually go to an XML-based
format? Then it might even need a complete re-write. That's why getting
a LaTeX to HTML converter that actually worked properly would really be
the best solution. Or so it seems to me.
rh
Abdel.
