On 2012/01/11 06:57:48, dak wrote:
On 2012/01/11 05:11:39, janek wrote: > There are some duplications in the docs now. > (LBTM?)
"The notation manual has not been revised yet."
Since I am currently doing the convert-ly rules for juggling the
argument order
and this will, obviously, also affect the manual both with respect to autoconversion as well as text sense, I am saving this for later. Of
course,
I'll be happy if someone else does the work on the NR, though of
course the
Scheme function documentation itself should match the code right away.
I've created http://code.google.com/p/lilypond/issues/detail?id=2213 so I'll work on the NR as I did all the \footnote Doc in the first place. I am assuming you still have to include your documentation edits in the patch so that the docs compile? Otherwise we will have a bit of a disconnect with the code and documentation until I push my patch. I'll try to get this done asap. On a 'merging' note, should I take the diff file from this tracker for the input.itely and use that as my base so that I don't end up with 'unable to apply' patch type messages on myside if I work from the *itely as it is in master? http://codereview.appspot.com/5527058/ _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
