On 11/28/2015 09:43 PM, Scott Kostyshak wrote: > On Sun, Nov 29, 2015 at 03:25:44AM +0100, Kornel Benko wrote: >> Am Samstag, > 28. November 2015 um 21:06:00, schrieb Scott Kostyshak <skost...@lyx.org> >>> Why doesn't LyX take care of updating the layout just as it takes care >>> of updating the .lyx file format? I ask this for both forwards and >>> backwards directions. I guess this means that lyx2lyx needs to know >>> where to find layout2layout. >>> >>> Is this just a missing feature or is there a reason things are how they >>> are? >>> >>> Scott >> >> Why should lyx do it? Layouts files are in the system lib, and this is not writeable by average user. > > Let's suppose just a user .lyx file, not a system .lyx file. For > example, if a user imports a .lyx file we update the .lyx file format. > Why don't we update the layout format?
The sensible reason is that there is no way to go backwards: Unlike with lyx2lyx, there is no possibility to go back to the old format, so we do not want to convert it to the new format. Note especially that this is true for "local layout": Once you manually update to the 2.2 layout format, there is no possibility to export a file to 2.1.x format. The local layout is not back-converted, so the file we export will not be readable by 2.1.x. We should probably issue a warning about this, but we've never had a bug report about it. > Conversely, when exporting from 2.2.0 to 2.1.x, we export the 2.1.x .lyx > > file format, but we do not convert the layout. The result of reverting to 2.1.x is supposed to work with 2.1.x, meaning: with the layout files that come with 2.1.x. That is why Uwe had to write code to revert the new Solution and Solution* environments: There are no layouts for those in earlier formats. So, in that sense, there's no need to revert layouts. Richard
