Greg Swinford <address@hidden> writes:
There is an error in the example given on the following documentation page:
http://lilypond.org/doc/v2.18/Documentation/notation/opera-and-stage-musicals#dialogue-over-music
\override LyricText.self-alignment-X = #LEFT should read
\override LyricText #'self-alignment-X = #LEFT
otherwise the following error occurs:
error: syntax error, unexpected '.', expecting SCM_FUNCTION or
SCM_IDENTIFIER or SCM_TOKEN
\with { \override LyricText
.self-alignment-X = #LEFT }
I presume the same error would occur with the font-shape definition above
this too, but I haven't tested this.
You are presumably testing with version 2.16 or earlier. If you take a
look at the corresponding documentation in
<URL:http://lilypond.org/doc/v2.16/Documentation/notation/opera-and-stage-musicals#dialogue-over-music>,
you'll find that it states
\new Lyrics \with {
\override LyricText #'font-shape = #'italic
\override LyricText #'self-alignment-X = #LEFT
}
here. The change is intentional. After considerable debate on the
mailing lists, it was implemented as issue
<URL:https://code.google.com/p/lilypond/issues/detail?id=2883>. This
upward-compatible syntax change was committed to version 2.17.6 almost
exactly 2 years ago, and the documentation has been changed to reflect
it.
Version 2.18 has been around quite a while now: updating to it makes
good sense. Particularly if you want to use its documentation...
Arguably, the new syntax is simpler to use. It has also made it
possible to let user-defined music functions accept such property
paths. So even while the old override syntax still works, there is
little point in using it in the documentation any more.