On Wednesday 31 March 2004 17:42, Georg Baum wrote: Georg I will apply your changes later or tomorrow. :-)
[...] > > I placed also convert and revert in the same file, as as far as > > possible I placed both implementation near each other. > > This is definitely an improvement, especially for symmetric changes > such as convert_spaces/revert_spaces. > > > The new files will be: > > lyx_0_12.py > > lyx_1_0_0.py > > lyx_1_0_1.py > > lyx_1_1_4.py > > lyx_1_1_5.py > > lyx_1_1_6.py > > lyx_1_1_6_3.py > > lyx_1_2.py > > lyx_1_3.py > > lyx_1_4.py > > I would like to see both ends of the conversion in the filename, e.g. > lyx_1_3_to_1_4.py. Otherwise, you can't see from outside which file > converts between two given versions: does lyx_1_3.py convert between > 1.2 <-> 1.3 or 1.3 <-> 1.4? In fact this has nothing to do with the > new naming scheme, I don't like the existing one either, because it > has the same problem ;-) I have to admit that lyx_1_3_to_1_4.py is no > good choice, because it implies that only one direction is possible, > but I have no better idea at the moment. Simple, you work with the lyx_1_4.py file during the 1.4 dev. cycle, we will work on the lyx_1_5.py file during the 1.5 cycle and so on. It is not so difficult after all. ;-) > > And those will replace all the existing lyxconvert* and > > lyxrevert* > > > > So, comments? > > Instead of the lines > > if format < 230: > format = 230 > > etc. I would rather print a warning that the conversion is not yet > implemented (only if a conversion is necessary of course). > This may annoy people enough so that they fix it. > In fact, I wrote the changes I sent because I got annoyed by "Missing > 'sideways' parameter" messages. Ok, I have implemented also the new API where we pass the opt struct, I will pass there the error chanel, that is or the standard error or a file that we choose, to be later seen in LyX. > Georg -- José Abílio LyX and docbook, a perfect match. :-)
