Re: Doc: Point-and-Click has wrong default value and ref to SVG output needs adding (issue 61630045)

LGTM, thanks. https://codereview.appspot.com/61630045/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Doc: Point-and-Click has wrong default value and ref to SVG output needs adding (issue 61630045)

Reviewers: lemzwerg, ul_openlilylib.org, Message: On 2014/02/10 19:34:46, ul_openlilylib.org wrote: mailto:lemzw...@googlemail.com schrieb: > https://codereview.appspot.com/61630045/diff/1/Documentation/usage/external.itely >File Documentation/usage/external.itely (right): > https://coder

Re: Doc: Point-and-Click has wrong default value and ref to SVG output needs adding (issue 61630045)

lemzw...@googlemail.com schrieb: > >https://codereview.appspot.com/61630045/diff/1/Documentation/usage/external.itely >File Documentation/usage/external.itely (right): > >https://codereview.appspot.com/61630045/diff/1/Documentation/usage/external.itely#newcode32 >Documentation/usage/external.itel

Doc: Point-and-Click has wrong default value and ref to SVG output needs adding (issue 61630045)

https://codereview.appspot.com/61630045/diff/1/Documentation/usage/external.itely File Documentation/usage/external.itely (right): https://codereview.appspot.com/61630045/diff/1/Documentation/usage/external.itely#newcode32 Documentation/usage/external.itely:32: in the @code{PDF} viewer. This ma

Re: NR: Removed example for alternate repeats (issue 61170044)

On Mon, 10 Feb 2014 04:31:25 -0800, wrote: These three examples are more useful as regression tests than as documentation. Are they robust enough? Do they exercise each property properly? They seem good enough, but it is not essential to add them to /input/regressoin/ They won't get lost,

Re: AccidentalCautionary in NullVoice

Hello, On 10 February 2014 02:19, Dan Eble wrote: > Here is a work-around for > https://code.google.com/p/lilypond/issues/detail?id=3834 which I suppose > suggests both a resolution and a reason not to make a distinction between > Accidental and AccidentalCautionary in the first place. (I unde

Re: CG: Add hints about using/adding images (issue 61540043)

fails make https://codereview.appspot.com/61540043/diff/1/Documentation/contributor/doc-work.itexi File Documentation/contributor/doc-work.itexi (right): https://codereview.appspot.com/61540043/diff/1/Documentation/contributor/doc-work.itexi#newcode1083 Documentation/contributor/doc-work.itexi:

CG: Add hints about using/adding images (issue 61540043)

Reviewers: , Description: CG: Add hints about using/adding images This is somewhat sketchy, but I can't afford to make this more thorouh ATM. Please review this at https://codereview.appspot.com/61540043/ Affected files (+25, -0 lines): M Documentation/contributor/doc-work.itexi M Document

Re: Add documentation for dodecaphonic-no-repeat (issue 61510043)

On 2014/02/10 12:50:27, J_lowe wrote: Thanks Urs. Some minor points. https://codereview.appspot.com/61510043/diff/1/Documentation/notation/pitches.itely File Documentation/notation/pitches.itely (right): https://codereview.appspot.com/61510043/diff/1/Documentation/notation/pitches.itely

Re: Add documentation for dodecaphonic-no-repeat (issue 61510043)

Thanks Urs. Some minor points. https://codereview.appspot.com/61510043/diff/1/Documentation/notation/pitches.itely File Documentation/notation/pitches.itely (right): https://codereview.appspot.com/61510043/diff/1/Documentation/notation/pitches.itely#newcode2453 Documentation/notation/pitches.i

Add documentation for dodecaphonic-no-repeat (issue 61510043)

Reviewers: , Message: This is an addition that David Nalesnik provided upon my request. I consider this a commonly used accidental style in contemporary music. Description: Add documentation for dodecaphonic-no-repeat Add dodecaphonic-no-repeat accidentalStyle This adds an accidental style th

Re: NR: Removed example for alternate repeats (issue 61170044)

On 2014/02/10 06:42:20, Keith wrote: I suggest just removing the obsolete text, and skipping the additions (unless you are worried that the manual is getting too short). :) Actually I think I had a conversation on similar lines with The Grand 'Foobar' himself (HRH Graham P), when I started.