Issue 243: really weird line breaks
http://code.google.com/p/lilypond/issues/detail?id=243
Comment #1 by [EMAIL PROTECTED]:
With ragged-right, lilypond should try and make the shortest system (except for
the
last one) as long as possible.
This would result in linebreaks inserted at the commented
Issue 139: tie misinterpreted as a slur
http://code.google.com/p/lilypond/issues/detail?id=139
Comment #7 by gpermus:
I don't see the fixes in 2.11.12.
Issue attribute updates:
Status: Started
--
You received this message because you are listed in the owner
or CC fields of this issue,
Issue 222: measure "numbers" in XML aren't actually numbers
http://code.google.com/p/lilypond/issues/detail?id=222
Comment #8 by gpermus:
I'll un-"Fixed" this last report, but in the future please file new
bug reports for
additional problems with music2xml.
Issue attribute updates:
Sta
Issue 238: Staff.keySignature wrong accidental numbers
http://code.google.com/p/lilypond/issues/detail?id=238
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 241: associatedVoice fails when switching back.
http://code.google.com/p/lilypond/issues/detail?id=241
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
Issue 237: melisma ends too early
http://code.google.com/p/lilypond/issues/detail?id=237
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 owner
or CC fields of this issu
Issue 236: set-octavation pitches operating in relative mode?
http://code.google.com/p/lilypond/issues/detail?id=236
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 own
Issue 235: stanza starting after first line does not have label printed
http://code.google.com/p/lilypond/issues/detail?id=235
Comment #2 by gpermus:
(No comment was entered for this change.)
Issue attribute updates:
Status: Verified
--
You received this message because you are listed
Issue 233: secondary beam on wrong side
http://code.google.com/p/lilypond/issues/detail?id=233
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 owner
or CC fields of thi
Issue 231: convert-ly and New_dynamic_performer
http://code.google.com/p/lilypond/issues/detail?id=231
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 field
Issue 230: segfault 2.11.10
http://code.google.com/p/lilypond/issues/detail?id=230
Comment #1 by gpermus:
Not fixed in 2.11.12. (sorry, I didn't check in 2.11.11)
Issue attribute updates:
Status: Started
Labels: -fixed_2_11_11 -fixed_2_10_11
--
You received this message becaus
Issue 229: Figured bass accidentals not being displayed
http://code.google.com/p/lilypond/issues/detail?id=229
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
Issue 215: #(layout-set-staff-size X) doesn't use pt as the scale
http://code.google.com/p/lilypond/issues/detail?id=215
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
Issue 138: single tie should use full tie-column formatting.
http://code.google.com/p/lilypond/issues/detail?id=138
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 owne
Issue 55: collision tie, accidental, and line break.
http://code.google.com/p/lilypond/issues/detail?id=55
Comment #8 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 f
Roland Goretzki wrote:
% The following shows wrong behaviour of extender line:
% If the piano has notes faster than melody, extender line doesn't work,
% and if the piano has notes as fast as or less fast than melody,
% e. l. does work.
This bug appears to be the same as 237, and is fixed in 2.
Frédéric Chiasson wrote:
Here is a code in which the accidentals are too close to the preceding
notes. When printed, the left accidentals touch the notes. Maybe it
would be
better to add more padding to the left of the accidentals (but that's my
opinion).
I think this is the same issue as the
Thanks for the report, this has been entered as
http://code.google.com/p/lilypond/issues/detail?id=244
Since this counts as a new feature and is an engraving nitpick, it may
be a while before it is implemented, but at least it's in the bug
tracker now.
Cheers,
- Graham
Marnen Laibow-Koser wr
Issue 244: rests can be too high in polyphony if voiceTwo is low
http://code.google.com/p/lilypond/issues/detail?id=244
New issue report by gpermus:
% rests-too-high.ly
% Rests in voiceOne are too high when voiceTwo is low.
\version "2.11.12"
\paper { ragged-right = ##t }
{
\time 3/4
<<
Thanks, entered as
http://code.google.com/p/lilypond/issues/detail?id=243
Cheers,
- Graham
Rune Zedeler wrote:
Rune Zedeler wrote:
\version "2.11.10"
{
\repeat unfold 5 c''1
% \break
\repeat unfold 12 c''1
% \break
\repeat unfold 62 c''64 c''32
c'4 c' c' c'
}
Whoops, forgot the p
Issue 243: really weird line breaks
http://code.google.com/p/lilypond/issues/detail?id=243
New issue report by gpermus:
\version "2.11.12"
{
\repeat unfold 5 c''1
% \break
\repeat unfold 12 c''1
% \break
\repeat unfold 62 c''64 c''32
c'4 c' c' c'
}
\paper {
ragged-right = ##t
indent = 8.
Thanks, added as
http://code.google.com/p/lilypond/issues/detail?id=242
Cheers,
- Graham
Frédéric Chiasson wrote:
Hi!
Here is a code that make some layout problems. With the sixteenth notes,
the
first beat chord's f is too close to the barline.
\version "2.11.11"
x = { 4 }
doubles = { c16
Issue 242: note too close to left barline
http://code.google.com/p/lilypond/issues/detail?id=242
New issue report by gpermus:
% the F in the chord is too close to the left barline.
\version "2.11.12"
x = { 4 }
doubles = { c16 c c c c c c c c c c c c c c c }
\new Score {
<<
\new Staff
Hi
On 1/18/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
Can you run the test procedure ... and
report whether it shows any unexpected problems?
Shure, I'll do it tomorrow.
Erlend
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- Code
Erlend Aasland escreveu:
> Hi,
>
> With 2.11.12, ties on notes between the two upper staff lines are too
> close to the staff lines (see attached bad.png). The attached patch will
> fix this (see attached good.png) but I haven't tested it much so it
> might not be the correct way to fix this.
>
Hi,
With 2.11.12, ties on notes between the two upper staff lines are too close
to the staff lines (see attached bad.png). The attached patch will fix this
(see attached good.png) but I haven't tested it much so it might not be the
correct way to fix this.
Regards,
Erlend
good.png
Descriptio
> I'm not top posting.
% I'm sorry, but it seems unpossible to make it shorter!
% The following shows wrong behaviour of extender line:
% If the piano has notes faster than melody, extender line doesn't work,
% and if the piano has notes as fast as or less fast than melody,
% e. l. does work.
\v
William Oram escreveu:
> I am not picky about standards. I will do whatever is functional and
> errorless. As it stands, there is no option that satisfies both.
>
> The options:
>
> a) \partial 4*3 r2 r4. Typographically correct (?), but -- and this is a
> big but! -- lilypond treats this as non-
Issue 214: two-pass spacing can stretch too much
http://code.google.com/p/lilypond/issues/detail?id=214
Comment #2 by erlenda:
(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 fiel
Lyrics attached to a Voice are center-aligned if attached to a single
note, and left-aligned if attached to a melisma. Lyrics attached to a
Devnull context, however, are always left-aligned. The following example
illustrates:
\version "2.10.11"
text = \lyricmode { foo bar baz quux }
notes = { c'4
On 2.10.11, running Documentation/user/lily-d5894a905a.ly results in these
warnings:
lily-d5894a905a.ly:1324:19: warning: Lyric syllable does not have note.
Use \lyricsto or associatedVoice.
lyr = \lyricmode {
I like my cat! }
lily-d5894a905a.ly:1324:21: warning: Lyric syllable
I can lecture about recitative time signatures, but I can't remember to
change e-mail subject lines. *sigh* Fixed.
---
I am not picky about standards. I will do whatever is functional and
errorless. As it stands, there is no option that satisfies both.
The options:
a) \partial 4*3 r2 r4. Typogr
I am not picky about standards. I will do whatever is functional and
errorless. As it stands, there is no option that satisfies both.
The options:
a) \partial 4*3 r2 r4. Typographically correct (?), but -- and this is a
big but! -- lilypond treats this as non-multimeasure-rest content, and
makes
Hi!
Here is a code in which the accidentals are too close to the preceding
notes. When printed, the left accidentals touch the notes. Maybe it would be
better to add more padding to the left of the accidentals (but that's my
opinion).
Frédéric
\version "2.11.11"
doubles = { c16 c c c c c c c
Hi!
Here is a code that make some layout problems. With the sixteenth notes, the
first beat chord's f is too close to the barline.
\version "2.11.11"
x = { 4 }
doubles = { c16 c c c c c c c c c c c c c c c }
\new Score
{
<<
\new Staff { \relative c' { \doubles | \doubles | \doubles }}
\new Sta
35 matches
Mail list logo
