Re: LM Errata
Jonathans and Max Many thanks for the help on the LM. I'm applying your changes at the moment. A few comments below. I'm not sure about mesh vs. match. Mesh has a lot of other meanings which could cause confusion, so maybe there's a better term or phrase to use there. I don't like mesh or match, so I changed the sentence to: The C++ language forces a certain method of grouping rules that cannot readily be applied to formatting music notation. Automated Engraving The first lilypond example in this section is missing. Do you mean the one introduced with Here you see two chords, with accents and arpeggios? If so, it seems to be present on the kainhofer server. What symbols to engrave? The third example in this section is missing. Again, it is there on kainhofer. How are you viewing these graphics? Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LM Errata
Automated Engraving The first lilypond example in this section is missing. Do you mean the one introduced with Here you see two chords, with accents and arpeggios? If so, it seems to be present on the kainhofer server. What symbols to engrave? The third example in this section is missing. Again, it is there on kainhofer. How are you viewing these graphics? Trevor I'm viewing from the web. Both show up on ie explorer but not on firefox (winxp sp3). -Jonathan ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LM Errata
Jonathan Wilkes wrote Tuesday, July 14, 2009 5:46 PM Automated Engraving The first lilypond example in this section is missing. Do you mean the one introduced with Here you see two chords, with accents and arpeggios? If so, it seems to be present on the kainhofer server. What symbols to engrave? The third example in this section is missing. Again, it is there on kainhofer. How are you viewing these graphics? Trevor I'm viewing from the web. Both show up on ie explorer but not on firefox (winxp sp3). They look fine here with both IE and Firefox (3.0.11) on Vista. Anyway, it doesn't seem to be a problem with the docs, so I'll go ahead and push the changes you suggested. You should be able to see them on kainhofer in a day or so. Thanks again for your help. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LM Errata
I'm viewing from the web. Both show up on ie explorer but not on firefox (winxp sp3). They look fine here with both IE and Firefox (3.0.11) on Vista. Anyway, it doesn't seem to be a problem with the docs, so I'll go ahead and push the changes you suggested. You should be able to see them on kainhofer in a day or so. I've upgraded Firefox to 3.0.11, and those sections I mentioned are still empty. Still looks fine in IE. Also, everything looks fine on a mac, so I'm not sure what could be causing that behavior. -Jonathan ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LM Errata
Jonathan Wilkes wrote Sunday, July 12, 2009 11:05 PM Hello, Here's errata for the LM. Some of these are very subjective, so just pick and choose what seems appropriate. Others are just typos or examples that aren't showing up. Many thanks for these corrections. A quick glance at them suggests they are all improvements, so I'll incorporate them into the docs when I get an hour or two to spare. Thanks for making the LM so nice! It will be even better soon, thanks to you! -Jonathan Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LM Errata
Jonathan Wilkes wrote: Hello, Here's errata for the LM. Some of these are very subjective, so just pick and choose what seems appropriate. Others are just typos or examples that aren't showing up. Thanks for making the LM so nice! -Jonathan 1.1 Background Engraving 1st paragraph: The plate would be inked, the depressions... to The plate would be inked, and the depressions... 1st paragraph: completely done to done completely 2nd paragraph: obvious advantages; (semicolon) to obvious advantages: (colon) 3rd paragraph: Our flat symbol is designed after, among others, this one. It is rounded, to Our flat symbol is designed after this one, among others. 5th paragraph The upper two measures are printed with this correction, the lower two measures without, forming down-stem/up-stem clumps of notes. to The upper two measures are printed with this correction; the lower two measures, however, form down-stem/up-stem clumps of notes. 6th paragraph so nitpicking about typographical details may seem academical. to so nitpicking typographical details may seem academic. 6th paragraph If a musician looks away once or has a lapse in concentration, the lines might lose their place on the page. to If a musician looks away once or has a lapse in concentration, he/she may easily lose their place on the page. This last one is grammatically incorrect, as it mixes singular (a musician, he/she) and plural (their). Better to say something like A distinct visual signature helps to keep musicians from losing their place [on the page] when they look away or have a lapse in concentration. Maybe even deleted the on the page part. Thanks for working on this, Jonathan. I guess everyone has to call me Jon now to avoid confusion. ;) Jon -- Jonathan Kulp http://www.jonathankulp.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LM Errata
6th paragraph If a musician looks away once or has a lapse in concentration, the lines might lose their place on the page. to If a musician looks away once or has a lapse in concentration, he/she may easily lose their place on the page. This last one is grammatically incorrect, as it mixes singular (a musician, he/she) and plural (their). Better to say something like A distinct visual signature helps to keep musicians from losing their place [on the page] when they look away or have a lapse in concentration. Ah, thanks. I overlooked their in the original, but it definitely flows better if everything is plural as above. I'm not sure about mesh vs. match. Mesh has a lot of other meanings which could cause confusion, so maybe there's a better term or phrase to use there. Maybe even deleted the on the page part. Thanks for working on this, Jonathan. I guess everyone has to call me Jon now to avoid confusion. ;) Jon -- Jonathan Kulp http://www.jonathankulp.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
