Bo Peng wrote: > > But we have to maintain backwards compatibility also within the 1.5 > > cycle. And is the backwards compatibility to 1.4 assured? I.e., will > > @extraparams be reverted to ERT correctly? > > I see a point here. When reverting to ERT, @ needs to be removed. I > will commit a patch soon.
No, that's wrong. > > IMHO , the only way to assure all this is to bump the file format > > _immediately_ and add a lyx2lyx reversion step that converts all listings > > insets that contain @extraparams to ERT. > > We already have lyx2lyx entries to convert InsetListings to ERT so I > will just modify them. You have to create another one. And you'll have to change the file format for every new parameter you will add in the future (to add the '@'). > Adding a separate entry will only benefit RC1 so I do not really want > to do that. Sure, if you use RC1 to open a file with @para, @para will > not pass validation. However, @para is supposed to be used when para > can not pass validation, so removing @ through lyx2lyx will not help. I didn't say removing. When @para is used, you'll have to transfer the whole listing to ERT for rc1 and friends, and include para (without the @). There's no other possibility IMO. > Cheers, > Bo Jürgen
