On 2009-09-17, rgheck wrote: > On 09/17/2009 09:02 AM, Jean-Marc Lasgouttes wrote: >> Alex Fernandez<alejandro...@gmail.com> writes:
>> This is where having built-in support for lyx2lyx would really >> increase confidence.It means that eLyXer will continue to work even if >> you do not update it for some release. In the current scheme, you >> would have to update it at each format change in trunk if you want it >> to work with trunk. I had this idea as well, but after looking more carefully at lyx2lyx, I do no longer see any benefit in *built-in* support for it. > I know you have made this suggestion before, but my sense is that the > design of elyxer makes lyx2lyx integration less helpful than it might > be. The same can be said to the design (and missing documentation) of lyx2lyx. Both, elyxer and lyx2lyx do a piecewise conversion of the document. They do not build an internal representation and write from this (like e.g. Docutils). Also, none of the two programs is intended to have a built-in interface. > What's true, of course, is that lyx2lyx integration would make it > possible to use elyxer with 1.7 files. Of course, you can do that anyway > by exporting to 1.6 and then running elyxer manually; if you had elyxer > configured as a LyX 1.6 --> HTML converter, I think that'd even happen > automagically. To improve the *LyX <-> elyxer* integration, I propose that elyxer provides a method and/or command line option that prints the supported input file formats. LyX's configuration script can use this to determine if pre-processing with lyx2lyx is needed. > 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.) > (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. However, "external lyx2lyx integration" will ensure, that the present feature set of elyxer is usable even with future LyX versions in the worst case scenario of no further maintenance. Günter > Richard
