Added
https://code.google.com/p/lilypond/issues/detail?id=4382
2015-04-27 20:44 GMT+02:00 Carl Sorensen :
> On 4/27/15 10:47 AM, "Federico Bruni" wrote:
>
> >2015-04-27 17:25 GMT+02:00 Kevin Barry :
> >
> >- I'd rather use a conversational approach instead of unordered lists:
> >"Please be awar
Dear Kevin,
> On Apr 27, 2015, at 10:18 AM, Kevin Barry wrote:
>
> The scope of the course will be to teach some of the finer points of
> engraving (Gould is the module reference text) and then get them to produce
> their own editions of out-of-copyright scores which we will then try to
> upl
On 4/27/15 10:47 AM, "Federico Bruni" wrote:
>2015-04-27 17:25 GMT+02:00 Kevin Barry :
>
>- I'd rather use a conversational approach instead of unordered lists:
>"Please be aware that LilyPond is a text-based(link) music engraver and
>read the FAQ(link) before...". "You can see LilyPond in action
2015-04-27 17:25 GMT+02:00 Kevin Barry :
>
> You know http://benlemon.me/blog/music/lilypond/operation-lilypond
>> ?
>
>
> No I didn't know about this, and thank you for linking it. I will take a
> good look.
>
This is listed here under "Other material":
http://www.lilypond.org/website/manuals.ht
On Mon, Apr 27, 2015 at 4:07 PM, Carl Sorensen wrote:
> Given the fact that you paid a price for not reading the Learning Manual
> more thoroughly, would it not make sense to use the Learning Manual as
> your text for the module? If there are problems with the Learning Manual,
> let's fix them.
On 4/27/15 7:18 AM, "Kevin Barry" wrote:
>
>3. Since I will, in effect, be creating a tutorial for new LilyPond
>users, perhaps I could encourage some collaboration here, and make the
>results freely available. MuseScore has an excellent series of tutorial
>videos, for example. I'm not necessaril
Hi Kevin,
Am 27.04.2015 um 16:18 schrieb Kevin Barry:
Dear All,
Three recent threads (are we the future, mutopia, and new users'
feelings about the docs) have prompted me to start a new one rather
than write separate replies to each. Apologies in advance for the
length, but I would be very g
