On 05/01/2011 04:49 PM, Jean-Marc Lasgouttes wrote: > Le 30/04/11 15:38, Richard Heck a écrit : >>> Would it be difficult to automate this? I was thinking that the best >>> solution to the problem, from a LyX point of view, was to provide---in >>> addition to the current message---a button that would download most >>> recent lyx2lyx from SVN or trac and place it to the appropriate >>> location in the profile folder. >>> >> Yes, though it seems kind of dangerous to download python scripts from >> the web and then offer to run them. > > IMO the problem is more what happens when someone hits this button > with LyX version 2.0 and current version is 4.1. Are we sure we have > kept the same interface to lyx2lyx? Are we going to be bound by that > forever? > > It looks like a complicated solution for a not so frequent problem. > That's my general sense, too: It's a corner case, and File>Export isn't that difficult.
For what it's worth, I don't really like the "save in the original format" idea either. It's nice that LyX can export to older formats, etc, but I'm not sure we really want to people to try to collaborate across major versions and then start reporting bugs when it doesn't work. There is just too much that can get lost when exporting to an older format. We know, in fact, that we do not always export usable documents to 1.6, and there is no way around that. Another issue is that LyX 2.0 documents might use modules (or other layout files, or local layout) that were introduced (or heavily modified) in LyX 2.0 and so are in the 2.0 format, not in the 1.6 format. There is no support in layout2layout for exporting to older formats, so this is another reason that exported documents might well not work properly without major intervention. People who want to collaborate with users of earlier versions (or use development versions for their own work, etc) should have the users of those earlier versions install their (newer) version of lyx2lyx. This isn't that hard to do, and it is by far the easiest solution. Richard
