* Chord names::
* Vocal music::
* Rhythmic music::
-* Tablatures::
+* Guitar ::
* Ancient notation::
* Other instrument specific notation::
@end menu
@code{\autochange} cannot be inside @code{\times}.
-Internally, the @code{\partcombine} interprets both arguments as
-@code{Voice}s named @code{one} and @code{two}, and then decides when
-the parts can be combined. Consequently, if the arguments switch to
-differently named @internalsref{Voice} contexts, the events in those
-will be ignored.
-
@node Manual staff switches
@subsection Manual staff switches
to a specialized function to change this behavior. For example, the
base can be printed in lower case.
+@cindex @code{chordPrefixSpacer}
+@item chordPrefixSpacer
+The ``m'' for minor chords is usually printed right after the root of
+the chord. By setting @code{chordPrefixSpacer}, you can fix a spacer
+between the root and ``m''. The spacer is not used when the root
+is altered.
+
@end table
The predefined variables @code{\germanChords},
-@code{\semiGermanChords} set these variables. The effect is
+@code{\semiGermanChords}, @code{\italianChords} and @code{\frenchChords}
+set these variables. The effect is
demonstrated here,
-@lilypondfile[raggedright]{chord-names-german.ly}
+@lilypondfile[raggedright]{chord-names-languages.ly}
There are also two other chord name schemes implemented: an alternate
Jazz chord notation, and a systematic scheme called Banter chords. The
@code{\germanChords},
@cindex @code{\semiGermanChords}
@code{\semiGermanChords}.
+@cindex @code{\italianChords}
+@code{\italianChords}.
+@cindex @code{\frenchChords}
+@code{\frenchChords}.
@seealso
-Program reference: @internalsref{DrumNoteEvent}.
+Program reference: @internalsref{note-event}.
@node Percussion staves
@subsection Percussion staves
The above example shows verbose polyphonic notation. The short
polyphonic notation, described in @ref{Polyphony}, can also be used if
-the @internalsref{DrumVoices} are instantiated by hand first. For example,
+the @internalsref{DrumVoice}s are instantiated by hand first. For example,
@lilypond[quote,raggedright,fragment,verbatim]
\new DrumStaff <<
-@node Tablatures
-@section Tablatures
+@node Guitar
+@section Guitar
@cindex tablature
@cindex guitar tablature
-Tablature notation is used for notating music for plucked string
-instruments. Pitches are not denoted with note heads, but by
-indicating on which string and fret a note must be played. LilyPond
-offers limited support for tablature.
-
@menu
+* String number indications::
* Tablatures basic::
* Non-guitar tablatures::
* Fret diagrams::
@end menu
+@node String number indications
+@subsection String number indications
+
+@cindex String numbers
+
+String numbers can be added to chords, by indicating the string number
+with @code{\}@var{number},
+
+@lilypond[relative,relative=1,raggedright,fragment]
+<c\1 e\2 g\3>
+@end lilypond
+
+See also @inputfileref{input/regression,string-number.ly}.
+
+
+@seealso
+
+Program reference: @internalsref{StringNumber},
+@internalsref{StringNumberEvent}
+
+
@node Tablatures basic
@subsection Tablatures basic
@cindex Tablatures basic
+Tablature notation is used for notating music for plucked string
+instruments. Pitches are not denoted with note heads, but by
+numbers indicating on which string and fret a note must be played. LilyPond
+offers limited support for tablature.
+
The string number associated to a note is given as a backslash
followed by a number, e.g., @code{c4\3} for a C quarter on the third
string. By default, string 1 is the highest one, and the tuning
Augmentum dots within ligatures are not handled correctly.
+The syntax still uses the deprecated infix style @code{\[ music expr
+\]}. For consistency reasons, it will eventually be changed to
+postfix style @code{note\[ ... note\]}. Alternatively, the file
+@file{gregorian@/-init@/.ly} can be included; it provides a scheme
+function
+@example
+\ligature @var{music expr}
+@end example
+with the same effect and is believed to be stable.
@menu
* White mensural ligatures::
\override NoteHead #'style = #'neomensural
\override Staff.TimeSignature #'style = #'neomensural
\clef "petrucci-g"
-\[ g\longa c\breve a\breve f\breve d'\longa \]
+\[ c'\maxima g \]
+s4
+\[ d\longa c\breve f e d \]
s4
-\[ e1 f1 a\breve g\longa \]
+\[ c'\maxima d'\longa \]
+s4
+\[ e'1 a g\breve \]
@end example
@lilypond[quote,raggedright]
\score {
\override NoteHead #'style = #'neomensural
\override Staff.TimeSignature #'style = #'neomensural
\clef "petrucci-g"
- \[ g\longa c\breve a\breve f\breve d'\longa \]
+ \[ c'\maxima g \]
+ s4
+ \[ d\longa c\breve f e d \]
s4
- \[ e1 f1 a\breve g\longa \]
+ \[ c'\maxima d'\longa \]
+ s4
+ \[ e'1 a g\breve \]
}
\layout {
\context {
\override NoteHead #'style = #'neomensural
\override Staff.TimeSignature #'style = #'neomensural
\clef "petrucci-g"
- \[ g\longa c\breve a\breve f\breve d'\longa \]
+ \[ c'\maxima g \]
+ s4
+ \[ d\longa c\breve f e d \]
+ s4
+ \[ c'\maxima d'\longa \]
s4
- \[ e1 f1 a\breve g\longa \]
+ \[ e'1 a g\breve \]
}
@end lilypond
@refbugs
-The implementation is experimental. It may output strange warnings,
-incorrect results, and might even crash on more complex ligatures.
+The invisible rests (@code{s4}) in the example are used to compensate
+for the poor horizontal spacing.
@node Gregorian square neumes ligatures
@subsubsection Gregorian square neumes ligatures
strings and text markups, see @ref{Overview of text markup commands}.
@example
-< [4 6] 8 [_! 12] > < 5 \markup{ + \number 6 } >
+< [4 6] 8 [_! 12] > < 5 \markup @{ + \number 6 @} >
@end example
@lilypond[quote,raggedright,fragment]
\context FiguredBass
projects / lilypond.git / blobdiff