From 161674c165e02bcf4b5d11500124c9f115228015 Mon Sep 17 00:00:00 2001 From: fred Date: Sat, 7 Apr 2001 23:30:08 +0000 Subject: [PATCH] lilypond-1.3.147 --- Documentation/user/GNUmakefile | 4 +- Documentation/user/lilypond-book.itely | 12 ++ Documentation/user/lilypond.tely | 5 +- Documentation/user/preface.itely | 30 ++- Documentation/user/tutorial.itely | 353 +++++++++++++++++++-------------- input/tutorial/GNUmakefile | 5 +- input/tutorial/lilbook.tex | 44 ++++ input/tutorial/sammartini.ly | 2 +- ly/script.ly | 12 +- 9 files changed, 291 insertions(+), 176 deletions(-) create mode 100644 input/tutorial/lilbook.tex diff --git a/Documentation/user/GNUmakefile b/Documentation/user/GNUmakefile index d36ffe5d6d..1dc1853f44 100644 --- a/Documentation/user/GNUmakefile +++ b/Documentation/user/GNUmakefile @@ -115,8 +115,8 @@ local-clean: rm -f fonts.aux fonts.log feta*.tfm feta*.*pk rm -rf $(outdir)/lilypond $(outdir)/lilypond-internals -$(outdir)/lilypond.nexi: $(outdir)/interfaces.itexi -$(outdir)/lilypond.texi: $(outdir)/interfaces.itexi +#$(outdir)/lilypond.nexi: $(outdir)/interfaces.itexi +#$(outdir)/lilypond.texi: $(outdir)/interfaces.itexi # Rules for the automatically generated documentation # When cross-compiling, we don't have lilypond, so we fake diff --git a/Documentation/user/lilypond-book.itely b/Documentation/user/lilypond-book.itely index f324d0e567..bfa123b1fe 100644 --- a/Documentation/user/lilypond-book.itely +++ b/Documentation/user/lilypond-book.itely @@ -246,6 +246,18 @@ commands. @code{\preLilypondExample} and @code{posLilypondExample} is defined to nothing by default, and the user can redefine them to whatever he wants. +@cindex titling and lilypond-book +@cindex lilypond-book and titling +@cindex \header in LaTeX documents + +If you want to combine music that has titling in @code{\header} +files, you should add the following to the top of your LaTeX +@example +\input titledefs.tex +\def\preLilypondExample@{\def\mustmakelilypondtitle@{@}@} +@end example + + @subsection Command line options diff --git a/Documentation/user/lilypond.tely b/Documentation/user/lilypond.tely index 1c88efb334..375272f238 100644 --- a/Documentation/user/lilypond.tely +++ b/Documentation/user/lilypond.tely @@ -71,7 +71,6 @@ this and other documentation. * Preface:: Preface. * Tutorial:: A tutorial introduction to LilyPond. * Reference Manual:: Reference Manual. -* Mutopia project:: Mutopia project. * Invoking LilyPond:: Operation. * Bug reports:: Where to report bugs. * ly2dvi:: Generating nice output with titles. @@ -80,7 +79,6 @@ this and other documentation. * lilypond-book:: Interleaving text with music. * Internals:: How it all works. * Literature:: Additional reading -* Full Grob interface list:: Generated list of all Grob properties. * Index of internals:(lilypond-internals). Auto generated detailed documentation. * Index:: Unified index. * Function Index:: Function index. @@ -96,7 +94,6 @@ this and other documentation. @mbinclude preface.itely @mbinclude tutorial.itely @mbinclude refman.itely -@mbinclude mutopia.itely @mbinclude internals.itely @mbinclude invoking.itexi @mbinclude bugs.itexi @@ -105,7 +102,7 @@ this and other documentation. @mbinclude lilypond-book.itely @mbinclude converters.itely @mbinclude literature.itely -@mbinclude interfaces.itexi + @c FIXME: Index has two alphabetically sorted lists @code vs plain? @node Index diff --git a/Documentation/user/preface.itely b/Documentation/user/preface.itely index 20a85a9ce3..2ddcf76b3a 100644 --- a/Documentation/user/preface.itely +++ b/Documentation/user/preface.itely @@ -4,17 +4,16 @@ It must have been during a rehearsal of the EJE (Eindhoven Youth -Orchestra), somewhere in 1994 that Jan, one of the cranked violists -told Han-Wen, one of the distorted french horn players, about the -grand new project he was working on. It was an automated system for -printing music (to be precise, it was MPP, a preprocessor for -MusiXTeX). As it happened, Han-Wen accidentally wanted to print out -some parts from a score, so he started looking at the software, and he -quickly got hooked. We soon realised that MPP was fundamentally -broken by design and it slowly died during 1995. We debated a lot -about the requirements to an inputformat, but that didn't produce any -new code. In 1996, Han-Wen started LilyPond. This time, Jan got -sucked into Han-Wen's new project. The rest is, as they say, history. +Orchestra), somewhere in 1995 that Jan, one of the cranked violists told +Han-Wen, one of the distorted french horn players, about the grand new +project he was working on. It was an automated system for printing +music (to be precise, it was MPP, a preprocessor for MusiXTeX). As it +happened, Han-Wen accidentally wanted to print out some parts from a +score, so he started looking at the software, and he quickly got hooked. +It was soon decided that MPP was a dead end. After lots of +philosophizing and heated e-mail exchanges Han-Wen started LilyPond in +1996. This time, Jan got sucked into Han-Wen's new project. The rest +is, as they say, history. You're reading the preface of the manual for LilyPond 1.4, which is in all honesty, the first release of LilyPond that combines stability, @@ -22,11 +21,10 @@ flexibility and good documentation. We hope you will have as much fun in using LilyPond as we have when hacking it. This manual was written to help you learn LilyPond, but as you might -imagine, we ourselves don't have much to learn about it. Therefore, -we can't really judge whether the manual is clear for a newbie, but -maybe you can! So, should you find any part of the manual vague or -outdated, please tell us your suggestions: if you don't, we'll never -know. +imagine, we ourselves don't have much to learn about it. We can't +really judge whether the manual is helpful for users, but maybe you can! +So should you find any part of the manual vague, unclear or outdated, +please let us know. Han-Wen and Jan diff --git a/Documentation/user/tutorial.itely b/Documentation/user/tutorial.itely index 09d60d1ed2..944fdb9142 100644 --- a/Documentation/user/tutorial.itely +++ b/Documentation/user/tutorial.itely @@ -2,8 +2,6 @@ @c TODO: LilyPond Lilypond lilypond -FIXME: choose one of: notation context/interpretation context. - @node Tutorial @chapter Tutorial @@ -36,7 +34,7 @@ yourself, to get a feel for how the program behaves. * A piano excerpt:: Piano music * An orchestral score:: * Other ways to run LilyPond:: -* Latex and texinfo integration:: +* Integrating text and music:: * end of tutorial:: The end @end menu @@ -445,7 +443,7 @@ identifier. @end example Here the music ends. LilyPond does not automatically typeset and end bar, we must explicitely request one, using @code{"|."}. -@c FIXME: Why not?! better to override \bar "" if not wanted? + @separate @example @@ -594,7 +592,7 @@ the @code{\header} block contains assignments. In each assignment, a variable is set to a value. Lexically, both the variable name and the assigned value are strings. The values have to be quoted here, because they contain spaces, the variable names could also be put within quotes -but it is not necessary. Each assignment is finished with a semicolon. +but it is not necessary. @separate @example @@ -646,10 +644,7 @@ beams off, and use explicit beaming where needed. @} @end example -This ends the definition of @code{melody}. Note that there are no -semicolons after assignments at the top level. - -[FIXME: no longer true for 146?] +This ends the definition of @code{melody}. @separate @example @@ -774,8 +769,9 @@ Normally, the notes that you enter are transformed into note heads. Note heads alone make no sense, they need surrounding information: a key signature, a clef, staff lines, etc. They need @emph{context}. In LilyPond, these symbols are created by objects called `interpretation -contexts'. Interpretation contexts (or `Notation contexts') only exist -during a run of LilyPond. +contexts'. Interpretation contexts exist for generating notation +(`notation context') and for generating sound (`performance +context'). These objects only exist during a run of LilyPond. By default, LilyPond will create a Staff context for you. If you would remove the @code{%} sign in the previous line, you would see that @@ -1838,18 +1834,6 @@ We specify a big indent for the first line and a small linewidth for this tutorial. @separate -@example - \translator@{ - \VoiceContext - \consists "Multi_measure_rest_engraver" - @} - \translator@{ - \HaraKiriStaffContext - \remove "Multi_measure_rest_engraver" - @} -@end example -[FIXME: ignoring mmrest moving for now, assuming we'll do that in -engraver.ly] Usually, LilyPond's predefined setup of notation contexts (Thread, Voice, Staff, Staffgroup, Score) is just fine. But in this case, we @@ -1939,15 +1923,13 @@ true. @node Other ways to run LilyPond @section Other ways to run LilyPond -[FIXME: describe all programs involved in one list.] - Until now, you have been using @file{ly2dvi} to invoke LilyPond. There are three other routes. Firstly, there is a script called @code{lilypond-book}, that allows you to freely mix LilyPond input with Texinfo or LaTeX input. For example, this manual was written using @code{lilypond-book}. It is discussed in @ref{lilypond-book}. -@c FIXME: ly2dvi option? + Secondly, you can generate PostScript directly. This is useful if you can not or do not want to run @TeX{} on your system. To obtain direct PostScript output, invoke LilyPond as follows: @@ -1959,24 +1941,197 @@ You have to set some environment variables to view or print this output. More information can be found in @ref{Invoking LilyPond}. -@c FIXME: ly2dvi option? + Thirdly, if you want to do special things with your output, you can run invoke lilypond directly: @example lilypond test.ly @end example -to produce plain @TeX{}@footnote{@TeX{} is a text-typesetting system -that is especially suited for typesetting mathematics.} output. Note -that you must run @TeX{} on the resulting @file{test.tex}, ie, not -LaTeX. +to produce plain @TeX{} output. Note that La@TeX{} will not work on the +resulting @file{test.tex}. You must run plain @TeX{} on it. + @cindex @TeX{} -@node Latex and texinfo integration -@section Latex and texinfo integration +@node Integrating text and music +@section Integrating text and music + +Sometimes, you might want to use music examples in a text that you are +writing. For example, if you are writing a musicological treatise, a +songbook, or (like us) the LilyPond manual. You can make such texts by +hand, simply by importing a PostScript figure into your wordprocessor. +However, there is a also an automated procedure: + +If you use La@TeX{} or texinfo, you can mix text and lilypond code. A +script called @code{lilypond-book} will extract the music fragments, run +lilypond on them, and put back the resulting notation. lilypond-book is +described fully in @ref{lilypond-book}, but here we show a small +example. Since the example also contains explanatory text, we won't +comment on the contents. + +@example +\documentclass[a4paper]@{article@} +\begin@{document@} + +In a lilypond-book document, you can freely mix music and text. For +example: +\begin@{lilypond@} + \score @{ \notes \relative c' @{ + c2 g'2 \times 2/3 @{ f8 e d @} c'2 g4 + @} @} +\end@{lilypond@} +Notice that the music line length matches the margin settings of the +document. + +If you have no \verb+\score+ block in the fragment, +\texttt@{lilypond-book@} will supply one: + +\begin@{lilypond@} + c'4 +\end@{lilypond@} + +In the example you see here, a number of things happened: a +\verb+\score+ block was added, and the line width was set to natural +length. You can specify many more options using \LaTeX style options +in brackets: + +\begin[verbatim,11pt,singleline, + fragment,relative,intertext="hi there!"]@{lilypond@} + c'4 f bes es +\end@{lilypond@} + +\texttt@{verbatim@} also shows the lilypond code, \texttt@{11pt@} selects +the default music size, \texttt@{fragment@} adds a score block, +\texttt@{relative@} uses relative mode for the fragment, and +\texttt@{intertext@} specifies what to print between the +\texttt@{verbatim@} code and the music. + +If you include large examples into the text, it may be more convenient +to put the example in a separate file: + +\lilypondfile[printfilename]@{sammartini.ly@} + +The \texttt@{printfilename@} option adds the file name to the output. + +\end@{document@} +@end example + +Under Unix, you can view the results as follows. +@example +$ cd input/tutorial +$ lilypond-book --outdir=out/ lilbook.tex +lilypond-book (GNU LilyPond) 1.3.146 +Reading `/home/hanwen/usr/src/lilypond-1.3.146/input/tutorial/lilbook.tex' +Reading +`/home/hanwen/usr/src/lilypond-1.3.146/input/tutorial/sammartini.ly' +@var{lots of stuff deleted} +Writing `out/lilbook.latex' +$ cd out +$ latex lilbook.latex +@var{lots of stuff deleted} +$ xdvi lilbook +@end example + +Notice the @code{outdir} option to lilypond-book. Running lilypond-book +and running latex creates a lot of temporary files, and you wouldn't +those to clutter up your working directory. Hence, we have them created +in a separate subdirectory. + +The result more or less looks like this: + +@separate + +In a lilypond-book document, you can freely mix music and text. For +example: +@lilypond + \score { \notes \relative c' { + c2 g'2 \times 2/3 { f8 e d } c'2 g4 + } } +@end lilypond +Notice that the music line length matches the margin settings of the +document. + +If you have no @code{\score} block in the fragment, +@code{lilypond-book} will supply one: + +@lilypond + c'4 +@end lilypond + +In the example you see here, a number of things happened: a +@code{\score} block was added, and the line width was set to natural +length. You can specify many more options using La@TeX{} style options +in brackets: + +@lilypond[verbatim,11pt,singleline, + fragment,relative,intertext="hi there!"] + c'4 f bes es +@end lilypond + +@code{verbatim} also shows the lilypond code, @code{11pt} selects +the default music size, @code{fragment} adds a score block, +@code{relative} uses relative mode for the fragment, and +@code{intertext} specifies what to print between the +@code{verbatim} code and the music. + +If you include large examples into the text, it may be more convenient +to put the example in a separate file: + +@lilypondfile[printfilename]{sammartini.ly} + +The @code{printfilename} option adds the file name to the output. +@node end of tutorial +@section The end + +That's all folks. From here, you can either try fiddling with input +files, or you can read the reference manual. You can find more example +files in @file{input} and @file{input/test}. You can also look at some +real music. Have a look at the @uref{Mutopia project, +http://www.mutopiaproject.org}. + + + +@ignore + +[TODO + +this should be on mutopia website. + +] + + +@c waar deze info? is uiteindelijk wel handig, schat ik. +[TODO: cut blabla] + +If you have a big music project, or just a lot of LilyPond input files, +all generated output from LilyPond, @TeX{} and metafont will clutter +your working directory. LilyPond comes with a one-size-fits-all +pre-cooked makefile that helps you manage producing output. It will +produce all output in the directory @file{out} , generate and track +dependencies. Also, it helps in preparing your submission to @ref{Mutopia +project}. + +@file{make/ly.make} +@example +mkdir my-project +cd my-project +cp /usr/share/lilypond/make/ly.make GNUmakefile +cp /usr/share/doc/lilypond/examples/input/tutorial/menuet.ly . +make menuet +[..] +Generated out/menuet.ps for target menuet. +@end example + +Type @samp{make help} to see possible targets. + +[TODO] +@file{/usr/share/lilypond/doc/lilypond/examples/input/mutopia-header.ly} + + + [TODO: rewrite completely.] @@ -1987,7 +2142,7 @@ LaTeX. So what does this look like? Well, here is an example: -@lilypond[veryverbatim, intertext="produces this music:"] +@li lypond[veryverbatim, intertext="produces this music:"] \score{ \notes\relative c'{ \time 5/8 @@ -2020,7 +2175,7 @@ music, another file than @code{paper16.ly} should be included. If you want to make the music not so wide, you can insert a @code{\paper} statement to set the linewidth: -@lilypond[veryverbatim, intertext="produces this music:"] +@li lypond[veryverbatim, intertext="produces this music:"] \score{ \notes\relative c'{ \time 5/8 @@ -2041,12 +2196,12 @@ If you only write voice-contents in the lilypond block, @command{lilypond-book} will set the @code{linewidth} variable to -1, so Lilypond will make the music as short as possible but without breaking the line. Here is a well know harmonic progression: -@lilypond[veryverbatim, intertext="produce a well known harmonic progression:"] +@li lypond[veryverbatim, intertext="produce a well known harmonic progression:"] \context Voice { } @end lilypond If you want to place music examples in the text, -@lilypond[eps] +@li lypond[eps] \context Voice { } @end lilypond , you can use the @code{eps} option. This will create the music as @@ -2055,14 +2210,14 @@ eps graphics and include it into the document with the The code used look like this: @example -@@lilypond[eps] +@@li lypond[eps] \context Voice @{ @} @@end lilypond @end example You can also use the @code{eps} option if the block is a complete lilypond source. This 5 cm long empty line, -@lilypond[eps] +@li lypond[eps] \score{ \notes{s} \paper{ linewidth = 5.\cm } @@ -2070,7 +2225,7 @@ lilypond source. This 5 cm long empty line, @end lilypond was created with this code: @example -@@lilypond[eps] +@@li lypond[eps] \score@{ \notes@{s@} \paper@{ linewidth = 5.\cm@} @@ -2082,8 +2237,10 @@ To avoid that La@TeX{} places the music on a line of its one, there should be no empty lines between the normal text and the lilypond environment. -You can also use @code{lilypondfile} (on a separate line, FIXME), to -include another file. +You can also use @code{lilypondfile}, to include another file: +@example + @@li lypondfile[printfilename]@{foo.ly@} +@end example @subsection Fontsize options @@ -2093,7 +2250,7 @@ the text, 11pt or 13pt is probably better. The code can look like this: @example -@@lilypond[13pt, eps] +@@li lypond[13pt, eps] @@end lilypond @end example @@ -2101,35 +2258,35 @@ The code can look like this: The following options set the fontsize: @itemize @item @code{11pt} -@lilypond[11pt, eps] +@li lypond[11pt, eps] \relative c'{ r16 [c d e][f d e c] [g'8 c][b-\prall c] | [d16 g, a b][c a b g][d'8 g f-\prall g] } @end lilypond @item @code{13pt} -@lilypond[13pt, eps] +@li lypond[13pt, eps] \relative c'{ r16 [c d e][f d e c] [g'8 c][b-\prall c] | [d16 g, a b][c a b g][d'8 g f-\prall g] } @end lilypond @item @code{16pt} -@lilypond[16pt, eps] +@li lypond[16pt, eps] \relative c'{ r16 [c d e][f d e c] [g'8 c][b-\prall c] | [d16 g, a b][c a b g][d'8 g f-\prall g] } @end lilypond @item @code{20pt} -@lilypond[20pt, eps] +@li lypond[20pt, eps] \relative c'{ r16 [c d e][f d e c] [g'8 c][b-\prall c] | [d16 g, a b][c a b g][d'8 g f-\prall g] } @end lilypond @item @code{26pt} -@lilypond[26pt, eps] +@li lypond[26pt, eps] \relative c'{ r16 [c d e][f d e c] [g'8 c][b-\prall c] | } @@ -2164,7 +2321,7 @@ La@TeX{} documents. It will also act as a simple test-suite for lilypond-book. You can place @code{eps} lilypond in and marginspars just as any other included eps graphics. -@lilypond +@li lypond \score{ \notes\relative c'{ \time 12/8 @@ -2185,7 +2342,7 @@ Danish composer Andy Pape. The music is put inside a the right margin if you set floatingfigure width and lilypond linewidth to the same value. The code looks like this: -@lilypond[verbatim] +@li lypond[verbatim] \score{ \notes\relative c'{ \time 12/8 @@ -2212,101 +2369,5 @@ Verbatim environments will also ignore the page margins. That is a feature of La@TeX{}. (But you usually put things inside a verbatim environment when you don't want La@TeX{} to do any linebreaking) -@node Songs with additional verses -@subsection Songs with additional verses - -With lilypond-book, you can typeset songs with additional verses. To -make lilypond-book print titles like ly2dvi, add - -[TODO: merge with lilypond-book tutorial] - - - - -@example -\input titledefs.tex -\def\preLilypondExample@{\def\mustmakelilypondtitle@{@}@} -@end example - -just before the music fragment. - -@c urg: can't show, won't work for .texi docs - -@example -% generate standard lilypond titles -\input titledefs.tex -\def\preLilypondExample@{\def\mustmakelilypondtitle@{@}@} - -\begin@{lilypond@} -\header @{ - title = "Title" - subtitle = "Subtitle" - subsubtitle = "Subsubtitle" - opus = "Opus 1" - piece = "Piece" - composer = "Composer" - enteredby = "JCN" - instrument = "instrument" -@} -\paper @{ linewidth = -1. @} -\score @{ - \notes \relative c'' @{ a b c d @} -@} -\end@{lilypond@} - -\begin@{enumerate@} -\item Verse one. aaa aaa aaa aaa aaa aaa aaa aaa aaa aaa -\item Verse two. bbb bbb bbb bbb bbb bbb bbb bbb bbb bbb -\end@{enumerate@} -@end example - - - -@node end of tutorial -@section The end - -That's all folks. From here, you can either try fiddling with input -files, or you can read the reference manual. You can find more example -files in @file{input} and @file{input/test}. You can also look at some -Real Music (TM), have a look at the @ref{Mutopia project}. - - - -@ignore - -[TODO - -this should be on mutopia website. - -] - - -@c waar deze info? is uiteindelijk wel handig, schat ik. -[TODO: cut blabla] - -If you have a big music project, or just a lot of LilyPond input files, -all generated output from LilyPond, @TeX{} and metafont will clutter -your working directory. LilyPond comes with a one-size-fits-all -pre-cooked makefile that helps you manage producing output. It will -produce all output in the directory @file{out} , generate and track -dependencies. Also, it helps in preparing your submission to @ref{Mutopia -project}. - -@file{make/ly.make} -@example -mkdir my-project -cd my-project -cp /usr/share/lilypond/make/ly.make GNUmakefile -cp /usr/share/doc/lilypond/examples/input/tutorial/menuet.ly . -make menuet -[..] -Generated out/menuet.ps for target menuet. -@end example - -Type @samp{make help} to see possible targets. - -[TODO] -@file{/usr/share/lilypond/doc/lilypond/examples/input/mutopia-header.ly} - @end ignore diff --git a/input/tutorial/GNUmakefile b/input/tutorial/GNUmakefile index 558771769c..45447ca2a5 100644 --- a/input/tutorial/GNUmakefile +++ b/input/tutorial/GNUmakefile @@ -1,6 +1,9 @@ depth = ../.. -LOCALSTEPMAKE_TEMPLATES=mutopia +LOCALSTEPMAKE_TEMPLATES=ly mutopia + +EXTRA_DIST_FILES=lilbook.tex + include $(depth)/make/stepmake.make diff --git a/input/tutorial/lilbook.tex b/input/tutorial/lilbook.tex new file mode 100644 index 0000000000..c64b11cc7c --- /dev/null +++ b/input/tutorial/lilbook.tex @@ -0,0 +1,44 @@ +\documentclass[a4paper]{article} +\begin{document} + +In a lilypond-book document, you can freely mix music and text. For +example: +\begin{lilypond} + \score { \notes \relative c' { + c2 g'2 \times 2/3 { f8 e d } c'2 g4 + } } +\end{lilypond} +Notice that the music line length matches the margin settings of the +document. + +If you have no \verb+\score+ block in the fragment, +\texttt{lilypond-book} will supply one: + +\begin{lilypond} + c'4 +\end{lilypond} + +In the example you see here, a number of things happened: a +\verb+\score+ block was added, and the line width was set to natural +length. You can specify many more options using \LaTeX style options +in brackets: + +\begin[verbatim,11pt,singleline, + fragment,relative,intertext="hi there!"]{lilypond} + c'4 f bes es +\end{lilypond} + +\texttt{verbatim} also shows the lilypond code, \texttt{11pt} selects +the default music size, \texttt{fragment} adds a score block, +\texttt{relative} uses relative mode for the fragment, and +\texttt{intertext} specifies what to print between the +\texttt{verbatim} code and the music. + +If you include large examples into the text, it may be more convenient +to put the example in a separate file: + +\lilypondfile[printfilename]{sammartini.ly} + +The \texttt{printfilename} option adds the file name to the output. + +\end{document} diff --git a/input/tutorial/sammartini.ly b/input/tutorial/sammartini.ly index 9b96735fad..8b1b54fe95 100644 --- a/input/tutorial/sammartini.ly +++ b/input/tutorial/sammartini.ly @@ -51,7 +51,7 @@ bassvoices = \notes \relative c' { \viola \oboes > - \context Staff = down < \time 2/2 \clef bass; + \context Staff = down < \time 2/2 \clef bass \bassvoices > > diff --git a/ly/script.ly b/ly/script.ly index 3407f96bc9..b0fcedd3dc 100644 --- a/ly/script.ly +++ b/ly/script.ly @@ -1,12 +1,12 @@ \version "1.3.146" -"dash-hat" = "marcato" -"dash-plus" = "stopped" -"dash-dash" = "tenuto" -"dash-bar" = "staccatissimo" -"dash-larger" = "accent" -"dash-dot" = "staccato" +dashHat= "marcato" +dashPlus= "stopped" +dashDash= "tenuto" +dashBar= "staccatissimo" +dashLarger= "accent" +dashDot= "staccato" thumb = \script "thumb" -- 2.11.4.GIT