I'm not overly enthusiastic about adding color to the manual: I'm not
certain how it will look in a printed pdf (many people print the docs)
or in the info files. We obviously need to use color in the doc section
about color, and the red staff-lines in Ancient notation will show up as
black anyway in print, but I'm worried about adding color to the main
manual.
Would it be possible to find noteheads that are more easily
distinguishable? Or perhaps making the example bigger?
...
Actually, I think the best solution is to move the basic explanation
about polyphony out of the manual and into the tutorial. I have no
problem with using bigger staff sizes in the tutorial, and I have less
concerns about using color in there. Also, that's the place for the
basic explanations.
Anybody feel like writing a wordy explanation about polyphony? It could
either replace/add to 2.3.4, or we could add a new subsection after
2.3.5 for this explanation. Feel free to plunder material from 6.3.3.
(if you do, please let me know before you start writing)
I don't mind doing this myself; I'm just asking in case Kieren is
excited about this topic. It would be a nice way to start working on
the docs. :)
Cheers,
- Graham
Mats Bengtsson wrote:
Excellent idea! I will add something like this to the manual, extended
with
yet another example that shows how to manually specify \voiceOne and
so on.
/Mats
Kieren MacMillan wrote:
Hi Mark,
It looks like there is a solution to the problem
Glad it worked!
perhaps people in the past just didn't understand the questions of
the people asking properly . . .
Perhaps... that's why I kept trying to clarify what question you were
really asking, so that I could answer the question you were really
asking! =)
Graham: may I suggest one thing that might help the docs? In 6.3
(especially .4, Explicitly instantiating voices), maybe if the notes
in each Voice context were independently (i.e., differently)
coloured, the examples (and thus the constructs and internal Lilypond
mechanisms) would be even more clear immediately?
For an example, see the attached snippet.
Best regards,
Kieren.
___
\version 2.11.30
\markup \wordwrap { At first it may be difficult to understand why
the three C notes are not tied in the following example: }
\score
{
\new Staff \relative c''
{
c ~ { c ~ } \\ { a } c }
}
\markup \wordwrap { By colouring the main Voice red, the problem
becomes clear: }
\score
{
\new Staff \relative c''
{
\override Voice.NoteHead #'color = #red
c ~ { c ~ } \\ { a } c
}
}
\markup \wordwrap
{
Within the \typewriter { \\\ } polyphony section, two
completely new Voice contexts, independent from the main Voice, have
been constructed automatically by Lilypond. There are several ways to
compensate for this instantiation, but the easiest is simply to avoid
the \typewriter { \\\ } construct entirely — within the
construct, any notes before an explicit \typewriter { \\new Voice }
command will belong to the main Voice context (i.e., the one
“outside” the polyphony):
}
\score
{
\new Staff \relative c''
{
\override Voice.NoteHead #'color = #red
c ~ { c ~ } \new Voice { a } c
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
