Well, in general, it is impossible to be backward compatible always. By this
I mean that changes to the file format cannot possibly be backward
compatible. The change we're discussing is just such a change. And, it was an
intelligent thing to do, making it easier to maintain the code base by having
one fewer special case.
There have not been many of these file format changes, however, so you've
been lucky. Note, however, that lyx may move very soon to an xml file format.
It will be possible to write a conversion script back to the old format, but
that'll be the best we can do, I suspect.
Can anybody think of any other changes in format?
Angus
On Monday 04 December 2000 17:51, Thomas Steffen wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
> > I'm not sure anybody promised backward compatability... Anyway, it's not
> > going to happen! Forward compatibility is Ok.
>
> Beg to differ. Forward compatibility is a must and therefore not worth
> mentioning. Backward compatibility is nice to have, and I would assume
> it between stable minor revisions. So far LyX *was* backward
> compatible, at least between the releases I have used (thats 1.0.1 to
> 1.1.5 IIRC). Remember the Word 97 thingy?
>
> > If you're not going to upgrade and use the same version of lyx on both
> > machines, then the following little file will do the trick:
>
> Obviously this is only the second best solution. It would certainly be
> nice to have this script in a complete form with some documentation in
> the distribution. Is this going to happen? If someone can point out
> the differences, I could at least collect them and try my best at a
> script (perl, that is :-)).
>
> > sed -f conv_new2old.sed < file_newformat.lyx > file_oldformat.lyx
>
> Or a couple of keystrokes on XEmacs, yes, that is always possible.
> Once you know what the problem is.
>
> Remainder: please drop me a copy as well, I'm not on the list.
>
> Thomas <[EMAIL PROTECTED]>
