Re: Using \tupletSpan causing bad output
On 01/03/13 16:33, Nick Payne wrote:
See attached.
\version "2.17.13"
\relative c'' {
\tupletSpan 8 \tuplet 3/2 { g8 fis e }
}
Forget about it. My bad. In the score where I encountered the output, I
forgot that I had changed from tuplets using sixteenth notes to tuplets
using eighth notes, and ignored the reason for the problem that was
staring me in the face when condensing to a minimal example.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Using \tupletSpan causing bad output
See attached.
\version "2.17.13"
\relative c'' {
\tupletSpan 8 \tuplet 3/2 { g8 fis e }
}
<>___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Typesetting Gregorian Chants
Francisco Vila writes: > 2013/2/28 Francisco Vila : >> I would like to cook a minimal example next. > > Attached are three compilable examples that show accidentals and morae bugs. Thanks once again, Francisco. I've created one new tracker for these three examples. https://code.google.com/p/lilypond/issues/detail?id=3215 Cheers, Colin. -- Colin Hall ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Typesetting Gregorian Chants
Francisco Vila writes: > 2013/2/28 Colin Hall : >>> Ok, you're right. The code is this and here you can view the result >>> https://www.dropbox.com/s/vp5hlx7gfuf91g1/Sanctus.pdf >> >> What is wrong with that output? Please be as precise as possible. > > About morae: (they should look like dotted notes) The two dots above > San- in the first *cough* measure belong and should go near previous > notes. > > Another example about morae that confuses spacing is at the end of > first line: a 'dotted' note produces the full barline to go right on > top of the note. > > About accidentals: look at first occurrence of Do - minus, right over > the hyphen: the flat is excessively far away from the note it belongs > to. Another example is in the second line over 'ri' in glo-ri-a : the > flat collides with the note it belongs to. Thank you, Francisco, that's just about perfect! Cheers, Colin. -- Colin Hall ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2.17.13 fails to build with texinfo 5.0 installed (texinfo 4.13 works)
Hanspeter Niederstrasser writes: > When texinfo 5.0 is installed, the build fails Thanks for reporting that build failure, Hanspeter. I will forward your post to the lilypond developer's mailing list. Cheers, Colin. -- Colin Hall ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Typesetting Gregorian Chants
Ok, you're right. The code is this and here you can view the result
https://www.dropbox.com/s/vp5hlx7gfuf91g1/Sanctus.pdf
THANKS
\version "2.16.0"
\header {
title = "Sanctus"
%subtitle = "Avvento"
%instrument = "Coro"
composer = "Gregoriano"
tagline = \markup \center-column { "Coro di Comunione e Liberazione,
Crema" \small "Nel limite umile del servizio alla Comunità " }
}
\markup { \vspace #2 }
\paper {
#(set-paper-size "a4")
}
\include "gregorian.ly"
\score {
<<
\new VaticanaVoice = "cantus" {
\clef "vaticana-do3"
%
http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Typesetting-Gregorian-chant
% Sanctus, Sanctus, Sancuts
\[ f \melisma \pes g a \flexa f g g \flexa \deminutum f \melismaEnd\] \[ f
\] \divisioMinima
\[ f \melisma \flexa \deminutum e \melismaEnd \] \[ \augmentum d \melisma
\flexa \augmentum c \melismaEnd \]
\[ f \melisma g \pes a c' \flexa a \virga a \inclinatum g \inclinatum f
\melismaEnd \] \[ \augmentum g \melisma \flexa \augmentum f \melismaEnd
\]\divisioMaior
% Dominus
\[ f \melisma \pes a c' \flexa bes \pes c' \melismaEnd \] \[ b \melisma\pes
a \melismaEnd\] \augmentum a
% Deus
\[ c' \] \[ bes \melisma\flexa a \melismaEnd\]
% Sabaoth
\[ g \melisma \flexa f g \pes a \flexa f \virga f \inclinatum e \inclinatum
d \] \[ f g \pes a c' \flexa a \virga a \inclinatum g \inclinatum f
\melismaEnd \] \[ g \melisma \flexa f \melismaEnd\] \augmentum f
\divisioMaxima
% Pleni sunt
f \[ a \melisma\pes c'\melismaEnd \] \augmentum c'
% caeli et terra
\[ a \melisma\flexa g \pes c' \melismaEnd\] \augmentum c' \[ c' \melisma
\pes \deminutum d' \melismaEnd \] \[ \virga d' \melisma \inclinatum c'
\inclinatum b c' \melismaEnd\] \[ \augmentum b \melisma \flexa \augmentum a
\melismaEnd\]
% gloria tua.
c' \[bes \melisma \flexa a \melismaEnd \] \[ g \melisma \pes a \melismaEnd
\] \[ \virga a \melisma \inclinatum g \inclinatum f \melismaEnd \]
\augmentum f\divisioMaxima
% Hosanna in excelsis.
f \[ f \melisma \flexa \deminutum e \melismaEnd \] \[ d \melisma \flexa c
\melismaEnd \] f \[ g \melisma \pes a \melismaEnd \] \[ a \melisma c'
\flexa a \virga a \inclinatum g \inclinatum f \melismaEnd \] \[ \augmentum
g \melisma \flexa \augmentum f s1\melismaEnd\]\divisioMaxima
% Benedictus qui venit
f \[ a \melisma \pes c' \melismaEnd \] \[ \virga c' \melisma \inclinatum a
\inclinatum g c' \melismaEnd \] \augmentum c' \[ c' \melisma \pes d'
\melismaEnd \] \[ \virga d' \melisma \inclinatum c' \inclinatum b c'
\melismaEnd \] \[ \augmentum b \melisma \flexa \augmentum a \melismaEnd \]
\divisioMinima
% in nomine Domini
a a f a \[ c'\melisma c' \pes d' \melismaEnd\] c' \augmentum c'
\divisioMaior
% Hosanna
c' \[ c' \melisma \pes d' \virga d' \inclinatum c' \inclinatum a bes
\melismaEnd \] \[ g \melisma \flexa f \melismaEnd \] \divisioMinima
% in excelsis.
\[ g\melisma\pes a\melismaEnd\]\[f\melisma\flexa
e\melismaEnd\]\[d\melisma\flexa c\]\[f g\pes a c'\flexa a \virga a
\inclinatum g \inclinatum f\melismaEnd\]\[\augmentum{g\melisma \flexa
f\melismaEnd}\]\finalis
}
\new Lyrics \lyricsto "cantus" {
San -- ctus, San -- ctus, San -- ctus
Do -- mi -- nus De -- us Sa -- ba -- oth.
Ple -- ni sunt cae -- li et ter -- ra glo -- ri -- a tu -- a.
Ho -- san -- na in ex -- cel -- sis.
Be -- ne -- dic -- tus qui ve -- nit in no -- mi -- ne Do -- mi -- ni.
Ho -- san -- na in ex -- cel -- sis.
}
>>
}
2013/2/28 Colin Hall
>
> Werner LEMBERG writes:
>
> >> I need to typesetting Gregorian, but I found two annoying bugs: the
> >> first is documented and concernes about the misplacing of morae, but
> >> the solution proposed doesn't work.
> >>
> >> The secondo is about the misplacing of accidentals. How can I
> >> workaround this two problems?
> >
> > Minimum sample *which compiles*, please.
>
> Marcello, as Werner said, we need more information from you.
>
> Here is a recent example of a good bug report:
>
> http://lists.gnu.org/archive/html/bug-lilypond/2013-02/msg00072.html
>
> That report includes a minimum sample (or "tiny example") and it also
> told us which version of Lilypond was used when the bug was noticed.
>
> There is more information on tiny examples here:
>
> http://www.lilypond.org/tiny-examples.html
>
> Cheers,
> Colin.
>
> --
> Colin Hall
>
--
m.
gplus.to/marcellotamburini
Pagina di "Sì, sono tutti miei":
https://plus.google.com/103735721672116039967
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
2.17.13 fails to build with texinfo 5.0 installed (texinfo 4.13 works)
When texinfo 5.0 is installed, the build fails with this error: /sw/build.build/lilypond-devel-2.17.13-1/lilypond-2.17.13/scripts/build/out/ run-and-check "LANG= makeinfo --enable-encoding --error-limit=0 -I /sw/build. build/lilypond-devel-2.17.13-1/lilypond-2.17.13/Documentation -I. -I./out -- output=out/lilypond-usage.info out/usage.texi" "usage.makeinfo.log" Please check the logfile usage.makeinfo.log for errors Documentation/usage.makeinfo.log contains the following: ***START*** out/common-macros.texi:190: warning: @end ifset should only appear at a line beginning out/usage/running.texi:31: warning: @vindex should only appear at a line beginning (possibly involving @rlearning) out/usage/running.texi:48: warning: @vindex should only appear at a line beginning (possibly involving @rweb) out/usage/running.texi:952: warning: @vindex should only appear at a line beginning (possibly involving @ruser) out/usage/running.texi:956: warning: @vindex should only appear at a line beginning (possibly involving @ruser) out/usage/running.texi:1125: warning: @vindex should only appear at a line beginning (possibly involving @ruser) out/usage/lilypond-book.texi:32: warning: @vindex should only appear at a line beginning (possibly involving @rweb) out/usage/lilypond-book.texi:32: warning: @vindex should only appear at a line beginning (possibly involving @rweb) out/usage/lilypond-book.texi:1177: @itemx must follow @item out/usage/lilypond-book.texi:1181: @itemx must follow @item out/usage/lilypond-book.texi:1185: @itemx must follow @item out/usage/lilypond-book.texi:1190: @itemx must follow @item out/usage/lilypond-book.texi:1199: @itemx must follow @item out/usage/lilypond-book.texi:1203: @itemx must follow @item out/usage/lilypond-book.texi:1208: @itemx must follow @item out/usage/lilypond-book.texi:1231: @itemx must follow @item out/usage/external.texi:274: warning: @vindex should only appear at a line beginning (possibly involving @rweb) out/usage/external.texi:323: warning: @vindex should only appear at a line beginning (possibly involving @rinternals) out/usage/external.texi:324: warning: @vindex should only appear at a line beginning (possibly involving @rinternals) out/usage/external.texi:587: warning: @vindex should only appear at a line beginning (possibly involving @rweb) out/usage/external.texi:607: warning: @vindex should only appear at a line beginning (possibly involving @ruser) out/usage/suggestions.texi:68: warning: @vindex should only appear at a line beginning (possibly involving @ruser) out/usage/suggestions.texi:119: warning: @vindex should only appear at a line beginning (possibly involving @ruser) ***END*** As mentioned in the summary, if texinfo is downgraded to 4.13, the build succeeds. Issues 1000 and 1557 are possibly related but they deal with texi2html 5.0 and not texinfo. Other possibly relevant software installed: texi2html: 1.82 dblatex: 0.2.12 texlive: 20110705 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Typesetting Gregorian Chants
2013/2/28 Francisco Vila : > I would like to cook a minimal example next. Attached are three compilable examples that show accidentals and morae bugs. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com gregorian1.ly Description: Binary data gregorian2.ly Description: Binary data gregorian3.ly Description: Binary data ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Typesetting Gregorian Chants
> To repeat: You have to create a *minimum* example, an example which > can't be further reduced without making the problem disappear [...] BTW, the only exception to this is support for visually handicapped or blind people (there are some such users on the lilypond mailing list). Werner ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Typesetting Gregorian Chants
> Ok, you're right. The code is this and here [...] Sorry, our help system doesn't work like this. To repeat: You have to create a *minimum* example, an example which can't be further reduced without making the problem disappear -- yes, this means extra work for you. And we need an *exact* description of the problem, ideally together with a scan from the literature which shows the correct solution. We are not paid for our service, everything is voluntary. So please be as helpful as possible to reduce the work of the people looking at *your* problem. Otherwise there are high chances that your request gets ignored completely. Werner ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Typesetting Gregorian Chants
2013/2/28 Colin Hall : >> Ok, you're right. The code is this and here you can view the result >> https://www.dropbox.com/s/vp5hlx7gfuf91g1/Sanctus.pdf > > What is wrong with that output? Please be as precise as possible. About morae: (they should look like dotted notes) The two dots above San- in the first *cough* measure belong and should go near previous notes. Another example about morae that confuses spacing is at the end of first line: a 'dotted' note produces the full barline to go right on top of the note. About accidentals: look at first occurrence of Do - minus, right over the hyphen: the flat is excessively far away from the note it belongs to. Another example is in the second line over 'ri' in glo-ri-a : the flat collides with the note it belongs to. I would like to cook a minimal example next. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Typesetting Gregorian Chants
Marcello Anselmi Tamburini writes: > 2013/2/28 Colin Hall > >> >> Werner LEMBERG writes: >> >> >> I need to typesetting Gregorian, but I found two annoying bugs: the >> >> first is documented and concernes about the misplacing of morae, but >> >> the solution proposed doesn't work. >> >> >> >> The secondo is about the misplacing of accidentals. How can I >> >> workaround this two problems? >> > >> > Minimum sample *which compiles*, please. >> >> Marcello, as Werner said, we need more information from you. >> >> Here is a recent example of a good bug report: >> >> http://lists.gnu.org/archive/html/bug-lilypond/2013-02/msg00072.html >> >> That report includes a minimum sample (or "tiny example") and it also >> told us which version of Lilypond was used when the bug was noticed. >> >> There is more information on tiny examples here: >> >> http://www.lilypond.org/tiny-examples.html >> > > > Ok, you're right. The code is this and here you can view the result > https://www.dropbox.com/s/vp5hlx7gfuf91g1/Sanctus.pdf What is wrong with that output? Please be as precise as possible. Also, please try to form a tiny example as described in the links I sent to you earlier. Cheers, Colin. -- Colin Hall ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Typesetting Gregorian Chants
Werner LEMBERG writes: >> I need to typesetting Gregorian, but I found two annoying bugs: the >> first is documented and concernes about the misplacing of morae, but >> the solution proposed doesn't work. >> >> The secondo is about the misplacing of accidentals. How can I >> workaround this two problems? > > Minimum sample *which compiles*, please. Marcello, as Werner said, we need more information from you. Here is a recent example of a good bug report: http://lists.gnu.org/archive/html/bug-lilypond/2013-02/msg00072.html That report includes a minimum sample (or "tiny example") and it also told us which version of Lilypond was used when the bug was noticed. There is more information on tiny examples here: http://www.lilypond.org/tiny-examples.html Cheers, Colin. -- Colin Hall ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Typesetting Gregorian Chants
> I need to typesetting Gregorian, but I found two annoying bugs: the > first is documented and concernes about the misplacing of morae, but > the solution proposed doesn't work. > > The secondo is about the misplacing of accidentals. How can I > workaround this two problems? Minimum sample *which compiles*, please. Werner ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Typesetting Gregorian Chants
Hi. I need to typesetting Gregorian, but I found two annoying bugs: the first is documented and concernes about the misplacing of morae, but the solution proposed doesn't work. The secondo is about the misplacing of accidentals. How can I workaround this two problems? Thank you. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
