On 07/12/2016 05:31 AM, José Abílio Matos wrote: > On Tuesday, July 12, 2016 6:20:38 AM WEST Richard Heck wrote: >> commit e57889ff2f38ed8e804a7e3c7e62114e31bf7715 >> Author: Richard Heck <rgh...@lyx.org> >> Date: Tue Jul 12 00:20:27 2016 -0400 >> >> Document new inverted branch insets in User Guide. Also add note to >> RELEASE_NOTES. > Since we are at the begin of the development cycle I would like to propose > the addition of new tests for the lyx upgrade format with the purpose of > having the lyx2lyx format equal to the format the lyx reads and writes.
There was some discussion of this last cycle, too, and I think everyone generally thinks it is a good idea. Exactly how to do it is less clear. I had thought about having, for each format change, test files that could be used to verify the forward and backward conversions for each format, but you are right that checking what happens with the User Guide (and for that matter our other documents) would be a good idea. > So given this motivation the method that I propose is the following: > > In order to simplify the explanation let us take this file format as an > example (upgrade to file format 511). > > In order to improve the test stage we need to keep a version of the UserGuide > of the last stable version around, in this case, UserGuide-22.lyx. > > The test consists then on three steps: > > 1) lyx2lyx -o UserGuide-23.lyx UserGuide-22.lyx > > 2) loads the resulting file UserGuide-23.lyx and forces write with lyx, > something like (I did not test the result): > > src/lyx -x 'command-sequence buffer-write-as UserGuide.lyx; lyx-quit' \ > UserGuide-23.lyx This actually exposes a different bug: Since the export happens in the background, we will immediately call lyx-quit. But we could fix that bug, or else modify the call. Richard
