James Harkins <[email protected]> writes:
> Urs Liska <ul <at> openlilylib.org> writes:
>
>> In the first line of that page you're directed
>> to
>> http://lilypond.org/doc/v2.16/Documentation/notation/special-characters#ascii-aliases
>> where the first example uses\paper {
>> #(include-special-characters)
>> }
>
> I see it now. It wasn't obvious to me that the special character
> aliases wouldn't work without enabling them in the paper block.
A list of ASCII aliases for special characters can be included:
\paper {
#(include-special-characters)
}
[...]
It does not get much more obvious than that.
> FWIW, I complain on the SuperCollider mailing list as well about
> "documentation by example." Examples are necessary but, if it's up to
> the reader to guess how something works based on an example, it leaves
> room to guess wrong. I don't mean this to say that the Lilypond
> manuals are misguided -- the opposite, actually: they're possibly the
> best documentation for any open source software I've used. This is a
> small gap. I'm just bored waiting to see Iron Man 3 and feel like
> pontificating about something :-P
Uh, you complain about the manual containing the information you were
needing? Are you sure this is a good choice for pontification?
--
David Kastrup
_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user
