Issue 197 in project lilypond

Issue 197: problem with lilypond-book naming schemes with multiple \scores http://code.google.com/p/lilypond/issues/detail?id=197 Comment #4 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are list

Issue 211 in project lilypond

Issue 211: cluster pieces don't join http://code.google.com/p/lilypond/issues/detail?id=211 Comment #1 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this

Issue 210 in project lilypond

Issue 210: clusters don't break correctly http://code.google.com/p/lilypond/issues/detail?id=210 Comment #1 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of t

Issue 193 in project lilypond

Issue 193: collision accidental fingering http://code.google.com/p/lilypond/issues/detail?id=193 Comment #3 by gpermus: I agree; there's still something wrong. New bug entered as 220; this current bug is closed. Issue attribute updates: Status: Verified -- You received this message b

Issue 220 in project lilypond

Issue 220: fingering too close to previous note http://code.google.com/p/lilypond/issues/detail?id=220 New issue report by gpermus: \version "2.11.8" \paper {ragged-right= ##t } \relative c'' { c4 c c \set fingeringOrientations = #'(left) } Issue attributes: Status: Acce

Issue 190 in project lilypond

Issue 190: Unexpected beam slanting in the opposite direction http://code.google.com/p/lilypond/issues/detail?id=190 Comment #3 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the own

Issue 154 in project lilypond

Issue 154: hairpin should end before a rest http://code.google.com/p/lilypond/issues/detail?id=154 Comment #2 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of

Issue 129 in project lilypond

Issue 129: tuplet bracket gets extended with partcombine http://code.google.com/p/lilypond/issues/detail?id=129 Comment #2 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or

Issue 93 in project lilypond

Issue 93: lyric extender going too far http://code.google.com/p/lilypond/issues/detail?id=93 Comment #5 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this

Re: Overlapping tuplets

Thanks, added as http://code.google.com/p/lilypond/issues/detail?id=219 Cheers, - Graham Rune Zedeler wrote: Simultainous tuplets are overlapping if the outermost tuplet is synced with a beam and hence no TupletSpanner is created. \version "2.11.8" { \times 4/7 { \times 4/5 { c'8 d' e' f'

Issue 219 in project lilypond

Issue 219: collision simultaneous tuplets http://code.google.com/p/lilypond/issues/detail?id=219 New issue report by gpermus: % Simultainous tuplets are overlapping if the outermost tuplet is % synced with a beam and hence no TupletSpanner is created. \version "2.11.7" \paper{ragged-right=##t}

Re: Linewidth -1 broken

Graham Percival escreveu: > Rune Zedeler wrote: >> Linewidth = -1 gives too tight spacing >> >> \version "2.11.8" >> { >> c' d' e'8 f' g' b' >> } >> \paper { line-width = -1 } > > What are you expecting from line-width = -1 ? I did a quick search to > see if -1 is supposed to mean "put everythi

Re: Linewidth -1 broken

Rune Zedeler wrote: Linewidth = -1 gives too tight spacing \version "2.11.8" { c' d' e'8 f' g' b' } \paper { line-width = -1 } What are you expecting from line-width = -1 ? I did a quick search to see if -1 is supposed to mean "put everything on one line", but I couldn't find any. Cheer

Linewidth -1 broken

Linewidth = -1 gives too tight spacing \version "2.11.8" { c' d' e'8 f' g' b' } \paper { line-width = -1 } -Rune ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond

Overlapping tuplets

Simultainous tuplets are overlapping if the outermost tuplet is synced with a beam and hence no TupletSpanner is created. \version "2.11.8" { \times 4/7 { \times 4/5 { c'8 d' e' f' g' } a' b' c'' } r2 } -Rune ___ bug-lilypond mailing list bug-lilyp

Issue 202 in project lilypond

Issue 202: merge-differently-headed should work for >2 voices http://code.google.com/p/lilypond/issues/detail?id=202 Comment #5 by Carl.D.Sorensen: FourVoicesOneStaff.png shows four, not three, voices. There are two full-time, staff-down voices in the measure. The opening staff-down note is a d

Re: "one big page" links broken

Le jeudi 04 janvier 2007 à 15:46 -0500, Michael Welsh Duggan a écrit : > The "one big page" links in the 2.11.8 English documentation (via > http://lilypond.org/doc/v2.11/Documentation/) are broken, leading to > the split versions. This bug is not new, just a silly conflict between lilypond/index.

Re: "one big page" links broken

Michael Welsh Duggan wrote: The "one big page" links in the 2.11.8 English documentation (via http://lilypond.org/doc/v2.11/Documentation/) are broken, leading to the split versions. Thanks for the report; the issue is caused from our work on the translation infrastructure. We are working on

"one big page" links broken

The "one big page" links in the 2.11.8 English documentation (via http://lilypond.org/doc/v2.11/Documentation/) are broken, leading to the split versions. -- Michael Welsh Duggan ([EMAIL PROTECTED]) ___ bug-lilypond mailing list bug-lilypond@gnu.org h

Issue 202 in project lilypond

Issue 202: merge-differently-headed should work for >2 voices http://code.google.com/p/lilypond/issues/detail?id=202 Comment #4 by gpermus: I'm not familiar with guitar notation, but FourVoicesOneStaff.png (I only see 3 voices, though) looks pretty good to me. This is a non-trivial feature reque

Re: Manual index entry for variable

Mats Bengtsson wrote: Graham Percival wrote: Thanks for the suggestion! I've added three index entries for these terms, although not to 2.18 -- we do not put index entries pointing to the tutorial. Why not? Sometimes, the best description is in the Tutorial. Good question. My initial mo

Issue 217 in project lilypond

Issue 217: Enter one-line summary http://code.google.com/p/lilypond/issues/detail?id=217 Comment #1 by gpermus: For more info about solution #1, see issue 218. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You ma

Issue 218 in project lilypond

Issue 218: center staccato over stem instead of notehead http://code.google.com/p/lilypond/issues/detail?id=218 New issue report by gpermus: It would be nice if staccato articulations were centered over a stem (or placed midway between the stem and notehead) instead of being centered on the noteh

Re: staccato dot in beam

Thanks for the report; added as http://code.google.com/p/lilypond/issues/detail?id=217 Cheers, - Graham Wilbert Berendsen wrote: I'm not top posting. The following example prints the staccato-dot too close to the beam. This could be solved in two ways: 1. print the staccato dot centered abo

Issue 217 in project lilypond

Issue 217: Enter one-line summary http://code.google.com/p/lilypond/issues/detail?id=217 New issue report by gpermus: % Wilbert Berendsen: %This could be solved in two ways: %1. print the staccato dot centered above the stem rather than the notehead %2. check for collisions with beams and increas

Re: layout-set-staff-size units

Mats Bengtsson wrote: - The text that I recently added to the manual is wrong, since it doesn't include the (* ... pt) to get the correct scaling. However, it seems more reasonable to change the function itself to use pt as the scale (the function is called internally at some places, which wou

Issue 216 in project lilypond

Issue 216: staff line spacing not changed inside \layout{} http://code.google.com/p/lilypond/issues/detail?id=216 New issue report by gpermus: The staff line spacing isn't changed unless you call the function within a \paper{...} block, which means that it cannot be used to produce different sta

Issue 215 in project lilypond

Issue 215: #(layout-set-staff-size X) doesn't use pt as the scale http://code.google.com/p/lilypond/issues/detail?id=215 New issue report by gpermus: % layout-set-staff should pt as the scale (the function is called % internally at some places, which would % have to be adjusted correspondingly)

Re: Two-pass page layout sometimes stretches too much.

Arvid Grøtting wrote: \paper { ragged-last-bottom = ##f texidoc = " Two-pass page layout sometimes stretches too much. When run without a tweak file, three pages of 3 + 3 + 2 systems are created. After two-pass space tweaking, I get five pages of 2 + 1 + 1 + 2 + 1 systems. Thanks for the

Issue 214 in project lilypond

Issue 214: two-pass spacing can stretch too much http://code.google.com/p/lilypond/issues/detail?id=214 New issue report by gpermus: % Arvid Grotting reported systems/page of 3+3+2 before and %2+1+1+2+1 after, using 2.11.5 % I just tried it with 2.11.7, and got 3+2+3 before and %2+1+2+3 after.