lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: doc reorg (especially Usage) possibly finished


From: Carl Sorensen
Subject: Re: doc reorg (especially Usage) possibly finished
Date: Sun, 27 Sep 2009 10:15:30 -0600



On 9/27/09 6:57 AM, "Graham Percival" <address@hidden> wrote:

> What do people think about the doc reorg shown in:
> http://kainhofer.com/~lilypond/Documentation/general/Manuals.html
> (and the actual manual pages, of course)
> 
> 
> I think I have the balance between Learning and Usage good now.
> The only remaining issues are:
> 
> 1) Learning B. Scheme tutorial -- do we want to keep this here, or
> integrate into Learning 4?  Or _possibly_ make a Learning 5
> Programming inside LilyPond?

I don't think we want to put this in the main body of the Learning Manual,
since we ask readers to read the LM cover to cover.  I think that having it
as an appendix is the right thing to do.  But I like the name Programming
inside LilyPond much better than Scheme tutorial.


> 
> 2) Was there some reason why all the indices are called "LilyPond
> index"?  I have a vaugue recollection that it worked better in the
> info format or something like that...?

index.html is the default page for a website.  Hence, we wanted LilyPond
index.


> If somebody could search the archives to look for any such reason,
> that would be nice.  If there's no such reason, then I'd rather
> rename them in some way.
> 
> 3) I'm not convinced about the order of material inside each
> chapter of Usage yet -- at the moment, I just want people to
> consider the division of stuff into chapters, not within each
> chapter.

I like the division of stuff into chapters.  Looks good!

I think there should be at least a pointer to OooLilyPond in Usage 3.2.,

I do have a minor nit to pick: on the Manuals page, the regular use section
is ordered Notation, Snippets, Usage, but the menu bar is ordered Notation,
Snippets, Usage.  All the rest are in order.

Thanks for your great work!

Carl





reply via email to

[Prev in Thread] Current Thread [Next in Thread]