rgheck schrieb:
My problem with the discussion in this thread is that it focuses on
the current state of eLyXer. But why is that important? eLyXer is not
yet ready for branch of course, but lets integrate it in trunk and
make it better. Before we release LyX 2.0 we can decide if eLyXer is
ready to be shipped together with LyX 2.0 or we disable it by changing
a few lines in configure.py.
Now I'm the one who doesn't see the advantage. And here's a reason not
to do it: If we put it in trunk, then we have to give commit rights to
anyone who wants to work on elyxer. Why should we do that? Why not just
leave it where it is?
We need to give Alex commit rights indeed but I don't see a problem. When I got commit rights, I
only got them because I developed the Windows installer. I trust Alex that he will not misuse his
rights. (Even if so, we can revert commits of block his account.)
And besides, the discussion has NOT just been about the current state of
elyxer. What emerged, and so far as I can tell Alex just agreed, is that
many of the things I was complaining elyxer can't do it will NEVER do,
both because of what he intends the program to be (simple, one-pass,
etc) and for reasons of principle (e.g., custom style can't be handled
without reading the LaTeX).
I like the way eLyXer goes. Over 90% of the LyX files users have doesn't use custom styles and the
like. For other cases one can use tex4ht. For PDF output we do the same - you can choose whether you
prefer ps2pdf or pdflatex.
But the main reason not to integrate elyxer is that we're likely to have
"built in" HTML output for 2.0.
Currently I don't see this coming. Nobody is currently working on this and José is very busy. So
having it included won't harm I think.
regards Uwe
