On 10/22/2009 05:53 PM, Alex Fernandez wrote:
On Thu, Oct 22, 2009 at 10:25 AM, Jean-Marc Lasgouttes
<lasgout...@lyx.org> wrote:
Le 22/10/2009 09:29, Abdelrazak Younes a écrit :
Right, it is different here as eLyXer cannot rely on LyX to do the
conversion. But it should be pretty easy to add a call to lyx2lyx before
conversion.
Yes. Alex, what is your take on this these days?
That, after skimming through the code of lyx2lyx, I am amazed that
anyone would think that eLyXer is hard work :)
Just joking. Since lyx2lyx seems to convert from standard input to
standard output, it would be trivial to make the converter line work:
lyx2lyx -V 277 -$$i | elyxer> $$o
I don't know if that line would work in Windows, but I guess eLyXer
might accept another option --lyx2lyx, or something.
JMarc, let me just remind you that this sort of maneouver has its
limits: New features will evaporate in a whirlwind of ERT, as will any
changes to semantics. Obviously, elyxer will still work with many files,
and will probably work OK with yet more files. But we do not accept this
kind of limitation where LyX itself is concerned, i.e., we demand that
1.7 files exported to 1.6 still work as expected, even if the document
is then awash in ERT.
The best solution, it seems to me, would be for elyxer to read the
format line and, if it is not to its liking, then it can call lyx2lyx
itself. But I'd guess this would be difficult to implement, since
finding lyx2lyx might not be so easy.
rh
