On 09/18/2009 03:26 AM, Guenter Milde wrote:
However, this will of course not enable elyxer to deal
with any 1.7-specific material, since that may just be converted to ERT,
and elyxer has little choice to but ignore ERT.
(Actually, elyxer could also parse and convert some ERT constructs. But I
suppose adding support for this ERT is more complicated than updating
elyxer to the new file format directly.)
What I meant was this: When a new feature is added, lyx2lyx generally
writes the raw LaTeX to ERT. Unless elyxer understands LaTeX, it will
not be able to do anything with this. Unless, of course, you added some
specific routine that recognized the sort of thing LyX would write. But
then you might as well just recognize the new LyX construct itself.
(LyXHTML export also ignores ERT, for the same reason, though that is
not an issue in this case.) So there's not really any way around
updating elyxer as the format changes.
Yes, both elyxer and LyXHTML will be incomplete in this sense and will
have to be maintained to keep up with new LyX features.
In the case of LyXHTML, this is no different from LaTeX export. People
who add new features will be expected to make sure that they work
properly with HTML export.
Richard
