On 04/29/2011 09:53 AM, Pavel Sanda wrote:
Tommaso Cucinotta wrote:
What is wrong with such an approach ?
The data loss thingy: it's very dangerous and naive users (but even
developers!) could suffer.
As far as the user is notified, I can't see a real problem here
unnoticed dataloss in your conversion step seems to me quite real
problem (and this can happen with backward lyx2lyx easily).
It shouldn't. One loses data in the sense that insets can get converted
to ERT, but you shouldn't lose data in any other sense.
couldn't you give your colleagues file exported to 1.6 on your side?
Can I raise a question again? Why not always backport changes to lyx2lyx
from trunk to branch? Of course branch releases will run slightly behind
trunk, but not so badly that it would be useless to do this. Then, to
some extent, the problem goes away, even without exporting.
Richard
