Sorry for the late reply. I'd prefer this as a @knownissues or even a @warning. I /definitely/ wouldn't include it in the same parapraph -- remember that the number of people reading a paragraph decreases exponentially as the length of the paragraph increases[1].
People normally wouldn't expect the order of the \includes to matter, so IMO we should make this quite visible. Cheers, - Graham [1] like all the best statistics in life, this is complete guesswork. However, I'd be willing to bet a modest amount that it's a fairly accurate guess. :) On Tue, Mar 10, 2009 at 07:38:50PM -0000, Trevor Daniels wrote: > Thanks Jon, pushed to origin/master > > Trevor > > ----- Original Message ----- From: "Jonathan Kulp" > <[email protected]> > To: "Trevor Daniels" <[email protected]> > Cc: "Carl D. Sorensen" <[email protected]>; "Valentin Villenave" > <[email protected]>; "David Kastrup" <[email protected]>; > <[email protected]> > Sent: Tuesday, March 10, 2009 2:59 PM > Subject: Re: Bug or feature? > > >> Patch attached. >> >> Jonathan >> >> On Tue, Mar 10, 2009 at 4:07 AM, Trevor Daniels >> <[email protected]>wrote: >> >>> >>> LGTM. >>> >>> Fancy doing a patch, Jonathan? >>> >>> Trevor >>> >>> ----- Original Message ----- From: "Carl D. Sorensen" >>> <[email protected]> >>> To: "Valentin Villenave" <[email protected]> >>> Cc: "David Kastrup" <[email protected]>; <[email protected]> >>> Sent: Sunday, March 08, 2009 7:58 PM >>> Subject: Re: Bug or feature? >>> >>> >>> >>> >>> >>> >>> On 3/8/09 11:13 AM, "Valentin Villenave" <[email protected]> >>> wrote: >>> >>> 2009/3/8 Carl D. Sorensen <[email protected]>: >>>> >>>>> Please file a simple bug report. I have a potential solution in >>>>> mind, and >>>>> hope to get it fixed in the next week or so. >>>>> >>>> >>>> Here you are: >>>> http://code.google.com/p/lilypond/issues/detail?id=763 >>>> >>>> I'd regard the \include thing as a bug too, but I'd need a more >>>> specific example. >>>> >>> >>> Lets call the \include thing a documentation bug. >>> >>> The solution is to change NR 1.1.1. Note names in other languages >>> >>> The current text is: >>> >>> There are predefined sets of note and accidental names for various >>> other >>> languages. To use them, include the language-specific init file >>> listed >>> below. For example, to use English notes names, add \include >>> "english.ly" >>> to >>> the top of the input file. >>> >>> The proposed new text is: >>> >>> There are predefined sets of note and accidental names for various >>> other >>> languages. To use them, include the language-specific init file >>> listed >>> below. For example, to use English notes names, add \include >>> "english.ly" >>> to >>> the input file. Because some other include files (such as >>> predefined-fretboards.ly) use default (Nederlands) note names, the >>> language >>> file should be \included after all other LilyPond distribution >>> files. >>> >>> >>> Thanks, >>> >>> Carl >>> >>> >>> >>> _______________________________________________ >>> lilypond-devel mailing list >>> [email protected] >>> http://lists.gnu.org/mailman/listinfo/lilypond-devel >>> >>> >> >> >> -- >> Jonathan Kulp >> http://www.jonathankulp.com >> > > > > _______________________________________________ > lilypond-devel mailing list > [email protected] > http://lists.gnu.org/mailman/listinfo/lilypond-devel _______________________________________________ lilypond-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-devel
