Re: doc addition: IR v2.20.0, 3.1.9 Arpeggio, positions
Hello Owain
On 26/08/2020 02:47, Owain Evans wrote:
Hi Bug-Lily,
In IR v2.20.0
3.1.9 Arpeggio, positions (pair of numbers),
http://lilypond.org/doc/v2.20/Documentation/internals/arpeggio
Says (left . right). Should read (bottom . top).
Please change to read:
Pair of staff coordinates (bottom . top), where both bottom and top are in
staff-space units of the current staff. For slurs, this value is (left-vertical
. right-vertical) and selects which slur candidate to use; if extreme positions
are requested, the closest one is taken.
"The for slurs part" I've change so it makes sense, but unsure if
"(left-vertical . right-vertical)" too verbose or correct naming convention.
An example of it so it's clear it's (bottom . top) not (left . right)
\version "2.20.0"
{
\override Staff.Arpeggio.positions = #'(-4 . 4)
\arpeggio
}
Please could it be corrected.
Many thanks,
Owain Evans
Thanks for taking the time.
https://gitlab.com/lilypond/lilypond/-/issues/6029
James
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
doc addition: IR v2.20.0, 3.1.9 Arpeggio, positions
Hi Bug-Lily,
In IR v2.20.0
3.1.9 Arpeggio, positions (pair of numbers),
http://lilypond.org/doc/v2.20/Documentation/internals/arpeggio
Says (left . right). Should read (bottom . top).
Please change to read:
Pair of staff coordinates (bottom . top), where both bottom and top are in
staff-space units of the current staff. For slurs, this value is (left-vertical
. right-vertical) and selects which slur candidate to use; if extreme positions
are requested, the closest one is taken.
"The for slurs part" I've change so it makes sense, but unsure if
"(left-vertical . right-vertical)" too verbose or correct naming convention.
An example of it so it's clear it's (bottom . top) not (left . right)
\version "2.20.0"
{
\override Staff.Arpeggio.positions = #'(-4 . 4)
\arpeggio
}
Please could it be corrected.
Many thanks,
Owain Evans
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Doc addition
Hi Squad, In LM 3.1.47 FretBoard ( http://lilypond.org/doc/v2.19/Documentation/internals/fretboard) I think it would be a good idea to add 'size' ; e.g. after 'stencil' or at last: size (number): The size, compared to the ‘normal’ size. 1 is style-sheet’s normal size, 0.8 is smaller, +0.1 is bigger. Negative numbers are not allowed. Cheers, Pierre ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Doc addition
I'm not top posting. Oops, sorry for 'not top posting'... See original question on the french list: http://lilypond-french-users.1298960.n2.nabble.com/diagramme-d-accords-td7583120.html Cheers, Pierre 2015-06-08 11:43 GMT+02:00 Pierre Perol-Schneider pierre.schneider.pa...@gmail.com: Hi Squad, In LM 3.1.47 FretBoard ( http://lilypond.org/doc/v2.19/Documentation/internals/fretboard) I think it would be a good idea to add 'size' ; e.g. after 'stencil' or at last: size (number): The size, compared to the ‘normal’ size. 1 is style-sheet’s normal size, 0.8 is smaller, +0.1 is bigger. Negative numbers are not allowed. Cheers, Pierre ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Doc addition
Thanks Pierre, added: https://code.google.com/p/lilypond/issues/detail?id=4438 Internals Reference is automatically generated and properties are listed alphabetically. I don't know why size is missing. This might be the case for other objects as well. Il giorno lun 8 giu 2015 alle 11:48, Pierre Perol-Schneider pierre.schneider.pa...@gmail.com ha scritto: I'm not top posting. Oops, sorry for 'not top posting'... See original question on the french list: http://lilypond-french-users.1298960.n2.nabble.com/diagramme-d-accords-td7583120.html Cheers, Pierre 2015-06-08 11:43 GMT+02:00 Pierre Perol-Schneider pierre.schneider.pa...@gmail.com: Hi Squad, In LM 3.1.47 FretBoard ( http://lilypond.org/doc/v2.19/Documentation/internals/fretboard) I think it would be a good idea to add 'size' ; e.g. after 'stencil' or at last: size (number): The size, compared to the ‘normal’ size. 1 is style-sheet’s normal size, 0.8 is smaller, +0.1 is bigger. Negative numbers are not allowed. Cheers, Pierre ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Doc addition
Pierre Perol-Schneider pierre.schneider.pa...@gmail.com wrote in message news:caphotuuunghjzxy-h-vekv5tvjfyjqpbbdtqieyy5homzck...@mail.gmail.com... Hi Squad please be so kind to add : http://lilypond.org/doc/v2.18/Documentation/snippets/staff-notation#staff-notation-time-signature-in-parentheses: and : http://lilypond.org/doc/v2.18/Documentation/snippets/staff-notation#staff-notation-time-signature-in-parentheses-_002d-method-3 into the Rhythms section : http://lilypond.org/doc/v2.18/Documentation/snippets/rhythms Cheers, Pierre Done for all three of the methods, although they won't actually appear in the documentation until there's an LSR import and a rebuild of LilyPond. -- Phil Holmes Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Doc addition
2014-02-22 15:37 GMT+01:00 Phil Holmes m...@philholmes.net: Done for all three of the methods, although they won't actually appear in the documentation until there's an LSR import and a rebuild of LilyPond. Thank you Phil ~Schneidy ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Doc addition
Hi Squad please be so kind to add : http://lilypond.org/doc/v2.18/Documentation/snippets/staff-notation#staff-notation-time-signature-in-parentheses: and : http://lilypond.org/doc/v2.18/Documentation/snippets/staff-notation#staff-notation-time-signature-in-parentheses-_002d-method-3 into the Rhythms section : http://lilypond.org/doc/v2.18/Documentation/snippets/rhythms Cheers, Pierre ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Notation Reference doc addition: Techniques Specific to Lyrics
Whoah, i thought that this was added to the docs long ago. I've wrapped it in a patch and put for review: http://codereview.appspot.com/8384043 (knowing myself, i've probably made some texinfo typos) best, Janek 2013/3/11 Colin Hall colingh...@gmail.com: Guy Stalnaker writes: Add to this page after the section for Divisi lyrics at the bottom: http://lilypond.org/doc/v2.16/Documentation/notation/techniques-specific-to-lyrics The following is based on this page for Temporary polyphonic passages. http://lilypond.org/doc/v2.16/Documentation/notation/multiple-voices I've created an issue tracker for your documentation suggestion, Guy. https://code.google.com/p/lilypond/issues/detail?id=3236 Thanks for your valuable contribution. Cheers, Colin. -- Colin Hall ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Notation Reference doc addition: Techniques Specific to Lyrics
Guy Stalnaker writes: Add to this page after the section for Divisi lyrics at the bottom: Thanks, Guy, nice work. Cheers, Colin. -- Colin Hall ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Notation Reference doc addition: Techniques Specific to Lyrics
Guy Stalnaker writes: Add to this page after the section for Divisi lyrics at the bottom: http://lilypond.org/doc/v2.16/Documentation/notation/techniques-specific-to-lyrics The following is based on this page for Temporary polyphonic passages. http://lilypond.org/doc/v2.16/Documentation/notation/multiple-voices I've created an issue tracker for your documentation suggestion, Guy. https://code.google.com/p/lilypond/issues/detail?id=3236 Thanks for your valuable contribution. Cheers, Colin. -- Colin Hall ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Notation Reference doc addition: Techniques Specific to Lyrics
Add to this page after the section for Divisi lyrics at the bottom:
http://lilypond.org/doc/v2.16/Documentation/notation/techniques-specific-to-lyrics
The following is based on this page for Temporary polyphonic passages.
http://lilypond.org/doc/v2.16/Documentation/notation/multiple-voices
Addition:
It is common in choral music to have a voice part split for a cadence,
or a measure or two. The {...} \\ {...} construct, where the two
(or more) musical expressions are separated by double backslashes, might
seem the proper way to set the split voices. This construct, however,
will assign *all* the expressions within it to *NEW Voice contexts*
which will result in *no lyrcis* being set for them since the lyrics
will be set to the original voice context--not, typically, what one
wants. The temporary polyphonic passage is the proper construct to use.
The temporary polyphonic passage construct format is:
code
{ \voiceOne ... }
\new Voice { \voiceTwo ... }
\oneVoice
/code
Note the absence of \\ after \voiceOne! The first expression within a
temporary polyphonic passage is placed into the Voice context which was
in use immediately before the polyphonic passage, and that same Voice
context continues after the temporary section. Other expressions within
the angle brackets are assigned to distinct temporary voices. This
allows lyrics to be assigned to one continuing voice before, during and
after a polyphonic section, but not the temporary voices.
The following example shows how to create a temporary polyphonic
(multi-voice) passage that will also set lyrics. If you normally create
voice and lyrics variables then construct the score using those
variables, the lyrics for a voice using this temporary polyphonic
passage construct will be set following \voiceOne.
code
verse = \lyricmode {
%Verse one snippet
Est et in -- ef --
fa -- bi -- lis
In di -- vi -- ni --
ta -- te.
%Verse two ending
An -- ti -- que de --
e --
rum.
}
bass = {
\key f \major
\time 4/4
\repeat volta 2 {
g,4 g, bf, bf, |
a, bf, c2 |
}
\alternative {
{ %First ending
c4 c bf, bf, |
c2 c
}
{ %Second ending
{ \voiceOne c4 c f f | ef2( df) | c1 }
{ \new Voice { \voiceTwo c4 c bf, g, | f,1 | f,1 \fermata } }
| \voiceOne
}
}\bar |.
}
bassPart = \new Staff
{ \clef bass \bass }
\addlyrics { \verse }
\score {
\bassPart
\layout { }
\midi { }
}
/code
Best regards,
Guy
--
There is only love, and then oblivion. Love is all we have
to set against hatred. (paraphrased) Ian McEwan
Guy Stalnaker
jimmyg...@gmail.com
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: doc addition
On Tue, Feb 28, 2012 at 12:12 AM, Janek Warchoł janek.lilyp...@gmail.com wrote: On Sat, Feb 25, 2012 at 8:19 AM, Janek Warchoł janek.lilyp...@gmail.com wrote: On Fri, Feb 24, 2012 at 1:23 AM, Colin Hall colingh...@gmail.com wrote: On Thu, Feb 23, 2012 at 11:18:43PM +0100, Thomas Morley wrote: Make sure you use convert-ly from the latest available release to gain all advantages from the latest converting-rules-updates. Thanks very much for the documentation suggestion, Thomas. I have created a new issue tracker for it, see Issue 2346 Rietveld issue added http://codereview.appspot.com/5696069/ The patch is being processed, i estimate it will take 2 more days before it reaches master. Thanks for your patience, Thomas. The patch is now in master (id 2411d0e11c5ca03997122c905bc2e58ea6a8682e). Unfortunately it narrowly missed 2.15.31 release, but there will be another release sooner or later. Thanks for your suggestion! Janek ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: doc addition
On Sat, Feb 25, 2012 at 8:19 AM, Janek Warchoł janek.lilyp...@gmail.com wrote: On Fri, Feb 24, 2012 at 1:23 AM, Colin Hall colingh...@gmail.com wrote: On Thu, Feb 23, 2012 at 11:18:43PM +0100, Thomas Morley wrote: Make sure you use convert-ly from the latest available release to gain all advantages from the latest converting-rules-updates. Thanks very much for the documentation suggestion, Thomas. I have created a new issue tracker for it, see Issue 2346 Rietveld issue added http://codereview.appspot.com/5696069/ The patch is being processed, i estimate it will take 2 more days before it reaches master. Thanks for your patience, Thomas. cheers, Janek ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: doc addition
On Fri, Feb 24, 2012 at 1:23 AM, Colin Hall colingh...@gmail.com wrote: On Thu, Feb 23, 2012 at 11:18:43PM +0100, Thomas Morley wrote: Make sure you use convert-ly from the latest available release to gain all advantages from the latest converting-rules-updates. Thanks very much for the documentation suggestion, Thomas. I have created a new issue tracker for it, see Issue 2346 Rietveld issue added http://codereview.appspot.com/5696069/ thanks, Janek ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
doc addition
Hi, In Contributor Guide 7.7 Updating LSR to a new version, below the paragraph: To update LSR, perform the following steps: 1.Download the latest snippet tarball, extract it, and run convert-ly on all files using the command-line option ‘--to=version’ to ensure snippets are updated to the correct stable version. please add: Make sure you use convert-ly from the latest available release to gain all advantages from the latest converting-rules-updates. Example:LSR-version: 2.12.2 intended LSR-update to 2.14.2 latest release 2.15.30 Use convert-ly from 2.15.30 and the following terminal command for all files: convert-ly -e -t2.14.2 *.ly Regards, Harm ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: doc addition
On Thu, Feb 23, 2012 at 11:18:43PM +0100, Thomas Morley wrote: Make sure you use convert-ly from the latest available release to gain all advantages from the latest converting-rules-updates. Thanks very much for the documentation suggestion, Thomas. I have created a new issue tracker for it, see Issue 2346 http://code.google.com/p/lilypond/issues/detail?id=2346 -- Colin Hall ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
