On Wednesday 10 December 2003 18:34, Angus Leeming wrote: > The attached patch changes the lyx format to 227 ... > However, I'll hold off applying it because I'm unsure how best to > proceed with lyx2lyx. The patch removes the just committed > lyxconvert_225.py, lyxrevert_226.py, moving their contents into the > new files lyxconvert_226.py, lyxrevert_227.py and augments these new > files with convert_box functions. However, I can see that this is > ugly.
Why do you want to move its content? I don't get your intent here... > Would it be best to do this only once we freeze for a 1.4 release so > that a released lyx2lyx would contain the equivalent of > lyxconvert_13xformat.py and lyxrevert_14xformat.py? No need, but if you want to... :-) > José, I wonder if the present scheme, where conversion to the latest > format is dictated by the names of the lyxconvert_xyz.py files would > not be better served by this in lyx2lyx: > > most_uptodate_format = 227 > > Thereafter, lyxconvert_225.py would just be a convenient placeholder > for all functions needed to convert format 225 to the > most_uptodate_format rather than conversion being implicitly defined > to produce format 226. The scheme we have is need to get the chain effect, we want to make the convertion from any given format to the intend by small steps. I have some preliminary support for 2.00 format, the first that I ever found, do you propose me to put all lyx2lyx scripts in the one used to convert that relic files to the present. And then when we have a new format we need to add those convertion functions also there. That is crazy. ;-) [Answered yesterday] -- José Abílio LyX and docbook, a perfect match. :-)
