Le 08/01/2016 22:26, Scott Kostyshak a écrit :
On Fri, Jan 08, 2016 at 11:06:04PM +0100, Georg Baum wrote:
Guillaume Munch wrote:
Also, because it took me a while to
figure out where the bind and ui format was defined. Nothing was
documented. (Is there a maintainer for Development.lyx who will validate
the CT'd changes?)
There is no maintainer for Development.lyx. Because of that and since it is
not supposed to be translated you don't need CT for this document IMHO.
+1. If you are just documenting something, go ahead. If you are
proposing a rule that LyX developers should follow, then this should be
discussed on the list but once there is agreement just commit (as Georg
says, no CT needed).
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
whenever a change to LFUNs requires a prefs2prefs_lfun update.
The reason for the LyX format increment is that updating Info insets by
hand in lib/doc is not enough, because it fails to take into account all
the LyX enthusiasts around the world who may have written their own LyX
documentation for their groups. So we rely on lyx2lyx for the conversion
and we duplicate code from prefs2prefs.
In particular, an increment to the LFUN format requires an increment to
the LyX format. There is an agreement from Georg, Jean-Marc and Richard;
and I did not see any opposition to this rule during the discussion of
this requirement for my patch.
Guillaume
