Le 12/01/2016 01:42, Pavel Sanda a écrit :
Guillaume Munch wrote:
Actually yes I am documenting a new rule, but it isn't mine. The new
rule requires a LFUN format increment and a LyX format increment
Do you have by chance link to LFUN format increment discussion at hand?
(I have no clue what is meant by LFUN format number). P
I think it started on the list but moved over to
http://www.lyx.org/trac/ticket/9794 during the ML shortage.
The LFUN format number is found in LyXAction.cpp and
prefs2prefs_lfuns.py, and is used for bind and ui files.
Here's the new text in Development.lyx:
“A change to the functionality of existing LFUNs can require a
conversion of .bind and .ui files, and therefore an increment of the
LFUN format, as well as a conversion of Info insets in .lyx files for
manuals. The latter cannot be done automatically and requires also a LyX
format increase (think of e.g. someone who might have made a set of LyX
teaching manuals for use in their own
group)[http://www.lyx.org/trac/ticket/9794].
1. Increment the LFUN file format number in src/LyXAction.h.
2. Implement the LFUN conversion in lib/scripts/prefs2prefs_lfuns.py
3. See step [enu:updatefiles] in section [subsec:update_lyx_files] but
instead of the updatedocs.py command, use this command: bash
development/tools/updatelfuns.sh.
4. Update Info insets in .lyx files. To do so, increment the LyX format
and proceed as in [subsec:update_lyx_files], steps
[enu:Describe_format]-[enu:updatefiles]. In the lyx2lyx implementation
([enu:Add-an-entry]th step), implement a conversion similar to the one
in prefs2prefs_lfuns.py above, as well as a corresponding reversion; for
this one can use convert_info_insets from lib/lyx2lyx/lyx2lyx_tools.py.”
