In a patch I submitted some days ago... http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=blobdiff;f=ly/music-functions-init.ly;h=1910975f7fdc81ff7e3632d766f396a631f62f06;hp=2dded22e3d77acd2b2dbcab500d6a01a5f893be9;hb=269248a11ada074066deb061d64df70ee7b4deec;hpb=53c3276a6d56cf8866f7f813d8b53f639bd6b073
I made this change in music-functions-init.ly:
-...@var{\addinstrumentdefinition}.")
+...@code{\addinstrumentdefinition}.")
Though the lilypond.org docs haven't been updated since, I see
now that the change has made it to Reinhold's docs:
http://kainhofer.com/~lilypond/Documentation/user/lilypond/Overview-of-available-music-functions.html#index-instrumentSwitch-2
However, the \a is still showing up as a control character 0x07,
which I'm assuming means "alarm"? It's listed as "bell" here:
http://www.fileformat.info/info/unicode/char/0007/index.htm
The html source also reads (with character 0x07 after <code>):
<code>ddInstrumentDefinition</code>
So, I'm sorry for the misstep, but I don't see why this happens.
By comparison, I grepped for @code{\a and found this example in
user/vocal.itely, line 168:
by the keyword @code{\lyricmode}, or by using @code{\addlyrics} or
which looks fine in the docs:
http://kainhofer.com/~lilypond/Documentation/user/lilypond/Entering-lyrics.html#Lyrics-explained
Can someone explain why it works in one file but not in the other?
I can patch a fix, but I'm not sure the right way to do it. I'm
guessing it's as simple as this:
-...@code{\addinstrumentdefinition}.")
-...@code{\\addinstrumentdefinition}.")
And if it is, here's the patch.
Thanks.
- Mark
0001-code-addInstrumentDefinition-code-addInstrumentDefin.patch
Description: Binary data
_______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
