Dear colleagues,
I don't understand your concerns: Whether eLyXer's approach is the right one to generate HTML out of
a LyX file or not doesn't currently matter.
The fact is that we currently don't have a feature that generates HTML. Our native HTML export is,
strictly spoken, currently vapor ware. We currently don't have something better than eLyXer so why
are you opposed to it?
The current discussion is similar to the one about green energy: We know we need to produce
electricity out of resources that doesn't produce pollution. As alternatives we have wind and solar
energy. But a windmill in front of your house is noisy and solar cells are not efficient enough in
northern countries. So you vote to build more coal power plants because of the disadvantages. Every
new approach has some disadvantage. Many of them will vanish by the time while some will stay. But
there is no reason not to give a new approach a chance, especially when it works.
Until we have native HTML export, we can have eLyXer in our SVN. When it comes to the point that we
think we cannot maintain eLyXer or when our HTML export is available _and_ produces better output,
we can move eLyXer to SVN's attic or remove it.
SVN is a repository for developing things, so why do you think it needs to be protected from new
code? When somebody makes a mistake you can correct it or revert the change. Having eLyXer for now
in SVN would help to give it at least a try.
regards Uwe
- Re: configure.py [patch] for branch Uwe Stöhr
-
