José Matos wrote: > On Wednesday 05 February 2003 13:18, Angus Leeming wrote: > There are lots of lessons to be learned from previous experience, so I > propose to increment the number file format every time that we make a > change. > > The alternative that table format implements is to have its own internal > number. But this is not needed most of the time. > > Or we could have a major and minor file format version number. What do > you (all of you, yes) think?
Well, that wasn't my intention in asking the original question, but major and minor versions make sense since that would allow you to define your linear series of converters 215.py, 216.py and have special code within them to deal with odd ball cases. No need, when converting from x to y, to go by way of x.3 if you can go straight to y. >> Does this mean that reLyX is already outputting tables in 216 format? > Nope, that is 215 format. So to be clear: 215 format == multicol5 but I have to make sure that reLyX does the things in your 215.py:update_tabular routine in order to output tables in 216 format? Do you have any example tables that get transformed by the code in 215.py:update_tabular? I thought that I'd take your incremental approach in trying to get reLyX to output moderm LyX (albeit a limited subset of it). -- Angus
