Re: Possible errors in the documentation

[Keith OHara]

Joram Berger <joram.noeck <at> gmx.de> writes:

> http://lilypond.org/doc/v2.16/Documentation/notation/writing-rhythms#scaling-
durations
> It is:
>   % Scale music by *2
> Should it be?
>  [ ... ]  % Divide durations by 2

The notes are typed printed as eighth-notes, but take up the time of 
quarter-notes, so their duration is increased.  "Scale music by *2"
is slightly awkward, but agrees with what happens, and the normal text
seems clear in both languages.
 
> http://lilypond.org/doc/v2.16/Documentation/notation/single-voice#chorded-
notes
>   <s f! \\ <e fis!> >>

Accident in the German translation.  It should be 
  << f! \\ <e fis!> >>

> http://lilypond.org/doc/v2.16/Documentation/notation/multiple-voices.html
> It is:
>   This example maps _four consecutive measures_ to four variables
> Should it be?
>   four voices? (or 2 consecutive measures?)

The intent is to say that 4 consecutive measures in the *input* are 
distributed into 4 voices, forming the first measure of the ensemble.
(Then the next 4 measures in the input provide the second measure for
each voice.)  

It is easier to show by example than to explain in text; the text 
is a mere introduction to the example.

> http://lilypond.org/doc/v2.16/Documentation/notation/displaying-staves
> Here, it is probably a translation problem:
> [ ... ] _bar_ lines (Taktstriche).
> (Btw. is that the only difference?)

Probably no-one knows from memory.  You can look in engraver-init.ly
to see the differences, and experiment to see if any other differences
are worth mention in the documentation.

> http://lilypond.org/doc/v2.16/Documentation/learning/modifying-context-
properties.de.html

reale Zahl  ->  reelle Zahl

> Is there a better/preferred way than the developers list to bring up
> issues like that?

Sending to -devel is fine.  You could have also sent this to -user for
discussion on what the documentation is trying to say.

When you are reasonably sure that some changes should be made, the best
way to have the corrections made, with lowest risk of being forgotten,
is to send exact, new, correct text in a message to bug-lilypond