Rob Lahaye <[EMAIL PROTECTED]> writes:
| Dekel Tsur wrote:
| > On Tue, Aug 20, 2002 at 10:22:58AM +0100, Angus Leeming wrote:
| > The code for compatibility read should not be in the lyx sources.
| > It is quite easy to do in lyx2lyx. If you don't know how,
| > write the differences between the old & new formats and I'll do it.
|
|
| Thanks Dekel!
|
| This means all the compatibility stuff can be removed from the code.
| When my patch is applied, the following changes are required:
|
|
| ------------------------------------------------------------------------------
| old-token new-token remove
| ------------------------------------------------------------------------------
| size_kind original / size_type 0 scale 100 width <val>
| height <val>
| scale <val>
|
| size_kind width_height / size_type 1 - scale <val>
|
| lyxsize_kind original / lyxsize_type 0 lyxscale 100 lyxscale <val>
| ------------------------------------------------------------------------------
| [replace old-token by new-token, and remove any following tokens as listed]
|
| (*) same applies to "size_type 0"
| (**) same applies to "size_type 1"
| (***) same applies to "lyxsize_type 0"
|
|
| Can you include this into lyx2lyx?
|
| BTW: we/I may have to push up the format version number, so that you can recognize
| the old from new format. That should come with my patch! But where in the code does
| that happen? And what are the rules for incrementing the format version?
Whenever you change the .lyx format increase the format version, _but_
during development this is not _really_ important, the important part
is to make sure that the version numver is increased for next stable
version.
--
Lgb
