Am 16.05.2015 um 13:48 schrieb Jean-Marc Lasgouttes:
I do not agree with your analysis, in particular since upgrading LyX on
an administrated linux machine is not always a given: the admin will
have to update LyX on all machines, and some users may not agree with that.
The question is then why not? This implies that the new LyX is buggy. It
is no problem to have 2 different LyX versions running parallel (I
always have 3: LyX 1.6, 2.0 and 2.1) so that some users can still the
old LyX while others can use the newer one.
However, this is not my point. I mostly collaborate with myself in LyX.
Last fall, when I began my 2.0 course stuff with LyX 2.1.2, it took my
some time to realize that the sweave stuff was not converted right. At
this point I had to downgrade to use 2.0.8. And actually this is when I
discovered that the reversion was wrong too for sweave chunks.
This is why I proposed to warn the user that his file will be saved in a
new format and why we should create a backup copy in the old format. In
case of problems the user can continue with the backup copy and the old
version. So no reversion is necessary. This also avoids cases where a
conversion was done. Then the user has problems and wants to revert but
this is buggy too. Then the user is lost if he did not make a backup
copy on his own.
Current policy:
- Assume that you have LyX 2.2 and your collaborator has 2.1. You add a
box with a 10 pt thick frame and export the document to the format of
LyX 2.1. As result you will get some TeX code. To be able to collaborate
you will have to live with that so in fact you cannot use the new
feature. So the situation is the same as if both persons collaborate
using both LyX 2.1. So what is the benefit from reverting new features
to TeX code?
The benefit is that we are not supposed to tell our users what they are
supposed to do. We actually do not know in what situation they are.
I don't understand.
Proposal:
- We keep our policy to provide a perfect roundtrip for features where
only the syntax changed, not the feature itself. Example: dash
conversion (formats 480<->481).
- We do no longer offer to revert new features if this would result in
Tex code.
- we keep our current policy for LyX 2.2 but change it for LyX 2.3.
Telling people that everything will still work when one upgrades is a
strong selling point IMO. If we lose that, people will be more reluctant
to upgrade.
Most people will only upgrade to get bugfixes and to benefit from the
new features. ("Never change a running system.")
I nevertheless think that creating a backup automatically when
converting files to a new version is the better solution in terms of
security not to loose any data.
The benefit for us is would be to save much work for lyx2lyx reversion
routines.
However, if you still disagree with me you might consider my proposal of
a warning for the users before a conversion takes place and an automatic
backup copy in the original format.
regards Uwe
