Jose' Matos wrote: > Yes, it can, but that is not the present behaviour. > For the present scheme to work you need to create a new file > lyxconvert_223.py and put there the convertion stuff.
See attached. Works perfectly.
> My question remains, why to change now? Was that intentional?
> Notice that I am not against it, if we decide that this is the way to
> go, good, you have my vote.
Shrug. It seems to me that we should increment the file format with every
change. We can always group multiple "development cycle lyxcvonverts"
together at a release if we are worried about too many files. I see already
that we don't have a specific lyxconvert_219.py for example.
>> Index: src/buffer.C
>> ===================================================================
>> namespace {
>>
>> -const int LYX_FORMAT = 223;
>> +const int LYX_FORMAT = 224;
>
> No problem here.
Good oh!
Lars, Ok to apply?
--
Angus
external.diff.gz
Description: GNU Zip compressed data
