James We've now had so many iterations of this I'd lost track of where we were up to with incremental changes and started over. I think much of it is improved, but some basic information has been lost and/or buried. I've tried to indicate as clearly (starkly might be more accurate) as possible what should be done to retrieve it.
Trevor https://codereview.appspot.com/120480043/diff/240001/Documentation/notation/input.itely File Documentation/notation/input.itely (right): https://codereview.appspot.com/120480043/diff/240001/Documentation/notation/input.itely#newcode2674 Documentation/notation/input.itely:2674: * Controlling MIDI dynamics:: I would put these in the order: The MIDI block Controlling MIDI dynamics MIDI instruments (taken from Enhancing MIDI output) Using repeats with MIDI Enhancing MIDI output (just the articulate script) https://codereview.appspot.com/120480043/diff/240001/Documentation/notation/input.itely#newcode2732 Documentation/notation/input.itely:2732: accent, marcato and portato. We need a proper list here showing clearly what is supported, so users new to midi output can see at the outset what it can do for them. I asked for this early in October ("The clear statement currently shown in NR 3.5.3 should be reinstated somehow, and reflected accurately in the text.") but I don't see it anywhere yet. The basic facilities can then be compared with the enhancements provided by the articulate script to see if that is going to be useful. https://codereview.appspot.com/120480043/diff/240001/Documentation/notation/input.itely#newcode2846 Documentation/notation/input.itely:2846: @rinternals{Dynamic_performer}. I don't think we need this reference here. https://codereview.appspot.com/120480043/diff/240001/Documentation/notation/input.itely#newcode2856 Documentation/notation/input.itely:2856: these should be entered in a @code{Staff} (not @code{DrumStaff}) context There seems to be a character that is not a space between "be" and "entered". https://codereview.appspot.com/120480043/diff/240001/Documentation/notation/input.itely#newcode2874 Documentation/notation/input.itely:2874: to match many articulation and tempo indications. Engraved output Most articulations are handled by the basic LilyPond performer. See and use NR 3.5.3. https://codereview.appspot.com/120480043/diff/240001/Documentation/notation/input.itely#newcode2912 Documentation/notation/input.itely:2912: @item Chords that are @emph{not} entered as chord names. Why is this basic information hidden in the articulate script and what does this item mean? Chords entered as notes _are_ supported. Consider a user who wanted microtonal chords. It says earlier microtones need a player that supports them. Ok, he says, I have that. Having tried to make it work for hours he now finds, buried in a @knownissues in a script he is not using, that microtonal chords are not supported. How is that an improvement to the documentation? What do you have against the clear lists in NR 3.5.3 presented at the top of the MIDI section? Why do you keep trying to suppress it with inaccurate and incomplete information distributed in several places? https://codereview.appspot.com/120480043/ _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
