Re: Protected Space Incompatibility Lyx 1.1.4fix3 and 1.1.5fix2
On Mon, Dec 04, 2000 at 06:19:08PM +, Angus Leeming wrote: > [snip] > > Can anybody think of any other changes in format? \paragraph_spacing (special spacing for the paragraph) > > Angus > -- Yves
Re: Protected Space Incompatibility Lyx 1.1.4fix3 and 1.1.5fix2
On Mon, Dec 04, 2000 at 07:49:19PM +0100, Lars Gullik Bjønnes wrote:
> Thomas Steffen <[EMAIL PROTECTED]> writes:
>
> | [snipped]
>
> Only if you define what minor revisions are... I am not sure the
> change from 1.1.4 to 1.1.5 is a minor revision (and please forget the
> numbers). 1.1.4 to 1.1.4fix1 is a minor revision I guess.
Debian stable has 1.1.4fix3, so I guess quite some people will be bitten
by the file format changes (it happened recentely to a coworker of mine).
>
> | So far LyX *was* backward
> | compatible, at least between the releases I have used (thats 1.0.1 to
> | 1.1.5 IIRC).
>
> This is only by coincidence.
> And probably not quite true either.
LyX 0.12.0 (at least) did use format 2.15.
I'd suggest an alert box if the file's lyxformat is greater than the
format recognized by LyX (currently a console ``ERROR'' message is output
if format - LYX_FORMAT > 0.05).
Attached is a patch for 1.1.5fix2; would you accept one for 1.1.6?
Beware--my patch is not sufficient: in 1.1.5, if a decimal
separator other than the point is used, Buffer::readFile will believe
lyxformat==2.00; thus no warning.
>
> | Remember the Word 97 thingy?
>
> What about it?
>
> Lgb
--
Yves
--- /home/stid/src/lyx-1.1.5fix2/src/buffer.C Fri Oct 13 14:25:42 2000
+++ /misc/rlin/home/zeb/src/lyx-1.1.5fix2/src/buffer.C Mon Dec 4 20:13:31 2000
@@ -1099,9 +1099,10 @@
printf(_("Warning: need lyxformat %.2f but
found %.2f\n"),
LYX_FORMAT, format);
}
- if (format - LYX_FORMAT > 0.05) {
- printf(_("ERROR: need lyxformat %.2f but found
%.2f\n"),
- LYX_FORMAT, format);
+ if (format > LYX_FORMAT) {
+ WriteAlert(_("Warning!"),
+ _("This document was created using
+a newer version of LyX."),
+ _("Please check for incorrect text
+or formating."));
}
bool the_end = readLyXformat2(lex, par);
// Formats >= 2.13 support "\the_end" marker
Re: Protected Space Incompatibility Lyx 1.1.4fix3 and 1.1.5fix2
Angus Leeming <[EMAIL PROTECTED]> writes: > 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. Yes, I understand that. And I am the last person to complain about a change to the better, even if it breaks backwards compatibility (Well ok, I *did* complain...). I was just puzzled by the fact that this is really the first file format problem ever that I came across, so I thought it might be a bug. > 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. Yes, that makes sense (though having real latex as a file format would suit me even more, but I guess you have discussed that quite a lot). > 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. That's ok. If it is documented somewhere. Just the one thing about Word 97 (8): remember the file format was incompatible with Word 6 or 7? Some people really got mad about it, because it was really difficult to interoperate. Later Microsoft did provide export and import of the other format, but the PR damage was already done. Thomas <[EMAIL PROTECTED]>
Re: Protected Space Incompatibility Lyx 1.1.4fix3 and 1.1.5fix2
Thomas Steffen <[EMAIL PROTECTED]> writes: | 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. Only if you define what minor revisions are... I am not sure the change from 1.1.4 to 1.1.5 is a minor revision (and please forget the numbers). 1.1.4 to 1.1.4fix1 is a minor revision I guess. | So far LyX *was* backward | compatible, at least between the releases I have used (thats 1.0.1 to | 1.1.5 IIRC). This is only by coincidence. And probably not quite true either. | Remember the Word 97 thingy? What about it? Lgb
Re: Protected Space Incompatibility Lyx 1.1.4fix3 and 1.1.5fix2
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]>
Re: Protected Space Incompatibility Lyx 1.1.4fix3 and 1.1.5fix2
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]>
Re: Protected Space Incompatibility Lyx 1.1.4fix3 and 1.1.5fix2
I'm not sure anybody promised backward compatability... Anyway, it's not
going to happen! Forward compatibility is Ok.
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:
conv_new2old.sed
# Replace all instances of
# xyz \SpecialChar ~
# abc
# with
# xyz
# \protected_separator
# abc
/[\]SpecialChar ~/{
s/[\]SpecialChar ~//
a\
\\protected_separator
}
Use as
sed -f conv_new2old.sed < file_newformat.lyx > file_oldformat.lyx
Angus
On Monday 04 December 2000 14:40, Thomas Steffen wrote:
> Hello,
>
> I use LyX 1.1.4fix3 at home and LyX 1.1.5fix2 at work, that is i386
> GNU/Linux Debian Potato and a current Debian Woody. Works like a
> charm, but: LyX 1.1.5 writes a construct that breaks 1.1.4:
>
> \layout Description
>
> a\SpecialChar ~
> b c
>
> LyX 1.1.4 expects:
>
> \layout Description
>
> a\proctected_separator
> b c
>
> Unfortunately, reading the first may mess up the following line as
> well, so that your document is really shredded.
>
> Since LyX has been very compatible between version so far, I would
> appreciate it, if LyX 1.1.5fix3 would be compatible with older version
> again.
>
> If you want to reproduce the bug: Open a new document in lyx 1.1.5,
> set style to description, type a word, type C-space (protected space),
> type another word, space, and another word. Save that document and try
> to load it with lyx 1.1.4.
>
> Please note that I am not subscribed to the list, sorry, and there is
> no archive. So please send me an email-copy. Apologies if the bug is
> already known.
>
> Thomas <[EMAIL PROTECTED]>
Protected Space Incompatibility Lyx 1.1.4fix3 and 1.1.5fix2
Hello, I use LyX 1.1.4fix3 at home and LyX 1.1.5fix2 at work, that is i386 GNU/Linux Debian Potato and a current Debian Woody. Works like a charm, but: LyX 1.1.5 writes a construct that breaks 1.1.4: \layout Description a\SpecialChar ~ b c LyX 1.1.4 expects: \layout Description a\proctected_separator b c Unfortunately, reading the first may mess up the following line as well, so that your document is really shredded. Since LyX has been very compatible between version so far, I would appreciate it, if LyX 1.1.5fix3 would be compatible with older version again. If you want to reproduce the bug: Open a new document in lyx 1.1.5, set style to description, type a word, type C-space (protected space), type another word, space, and another word. Save that document and try to load it with lyx 1.1.4. Please note that I am not subscribed to the list, sorry, and there is no archive. So please send me an email-copy. Apologies if the bug is already known. Thomas <[EMAIL PROTECTED]>
