Re: docs

[Graham Percival]

On 30-Aug-05, at 3:38 AM, Hans de Rijck wrote:

> Please add to index:
> \afterGrace

Done.

> \stemUp
> \stemDown

I'm not certain about these.  I commented out the section on setting 
stem
directions, since that section isn't useful.  I suppose I could include 
that
info in the section on polyphony.

I would rather include a section that listed all the contents of
ly/property-init.ly , but I'm not certain how to include that in the 
docs (from
a technical standpoint).

> 6.5.1 Articulations
>
> In the chart showing all scripts available, can there be some spacing
> between the words, they are now almost impossible to decipher, for 
> example
> the third line reads:
>    rheelltoertoeopenstoppedturnreverseturn

I'm accepting suggestions.  This example is created from 
input/test/script-chart.ly ;
the names are done as lyrics.  How can you space out lyrics ?

> 6.5.3 Dynamics
>
> Please add a line how to get dynamics aligned. It's now very implicit.

Please tell me how to.  :)

> What I mean is, your example
>     c\< c\! d\> e\!
> leads to a crescendo and a decrescendo that don't align (very ugly!).
> If you do a small concession and write:
>     c\< c\! \> d e\!
> they are perfectly aligned. Of course it would be better if you could 
> order
> lilypond to automatically align dynamics, but we can't have it all.

I'm reluctant to do this, because it has a different musical meaning 
(ie the
decresc starts on the c, not the d).  Currently the manual example 
demonstrates
the way lilypond handles most cresc/decresc.  I think the best way to
handle this is to improve lilypond's cresc handling, as Trevor 
suggested.


> 10.1.3 Page formatting
>
> can these subcommands be added to the index?

> 10.1.9
>
> can raggedright be added to the index? took me half an hour to find it.
>
> 10.1.13 Creating titles
>
> can these subcommands be added to the index?

ok, done.

> Can the picture be centered? In printed PDF it falls off the left of 
> the
> page.

Accepting suggestions as to how.  :(

>  Also in this example the lilypond example suggests that in 'opus'
> different fontsizes are used, but in the result this is not visible

Ah, yes.  opus isn't printed at all; I've changed the example to the
arranger field.

> I hope this is of help,

Yes, thanks.  Note that I've only updated the 2.7 manual.

Cheers,
- Graham