On 10/23/2009 03:38 PM, Alex Fernandez wrote:
On Fri, Oct 23, 2009 at 12:36 AM, rgheck<rgh...@bobjweil.com> wrote:
Producing HTML output by parsing LyX documents is what eLyXer does. It
has so far proved to be an interesting challenge, and in my biased
opinion the results are better than any TeX->HTML converters or than
native HTML output from within LyX.
Since the native HTML output from within LyX isn't fully implemented (to say
the least), that is not a fair comparison. Once it has been, then there will
be something to discuss.
That is kind of the point: native HTML output has been in the works
for a long time and it has not given the expected results. Now, I
don't know how much time you have devoted to it; but my guess is that
the problem is much more complex than what eLyXer set out to solve.
This is a bad guess.
First, native HTML output has been worked on, by me, for a handful of
hours. Then I got busy with other things and set it aside, as indeed I
have had to set aside other work on LyX.
Second, as Pavel and I have been saying, there is no conceivable way
that doing HTML output from within LyX could be harder than parsing the
file format. This is so patently obvious (at least to those of us who
actually know something about how LyX works) that it is not worth
discussing.
But whatever. We've been over this ground before, as Pavel said, and I
certainly have no interest in rehashing it. Nor, I'm guessing, does anyone
else.
If you have no interest in rehashing it, then don't; but please do not assume
that nobody else is.
Do as you wish. We (the people who actually work on LyX, as opposed to
merely whinging) have made up our mind about the integration question
and all others at issue here. That's why I shan't be bothered.
rh
