Updates:
Status: Fixed
Labels: fixed_2_13_12
Comment #4 on issue 880 by n.puttock: Regression: Arpeggios collide with
notes when connectArpeggios is set
http://code.google.com/p/lilypond/issues/detail?id=880
(No comment was entered for this change.)
--
You received this messa
Updates:
Status: Fixed
Labels: fixed_2_13_12
Comment #4 on issue 821 by n.puttock: Regression: arpeggios may collide
with barlines in a PianoStaff with multiple voices
http://code.google.com/p/lilypond/issues/detail?id=821
(No comment was entered for this change.)
--
You rece
Updates:
Status: Fixed
Owner: n.puttock
Labels: fixed_2_13_12
Comment #2 on issue 981 by n.puttock:
input/regression/fermata-rest-position.ly
http://code.google.com/p/lilypond/issues/detail?id=981
This is caused by the fix for #495 (2.11.36), which
added 'outside-sta
Updates:
Status: Fixed
Owner: n.puttock
Labels: fixed_2_13_12
Comment #2 on issue 986 by n.puttock: collision tuplet number and
partcombine text
http://code.google.com/p/lilypond/issues/detail?id=986
(No comment was entered for this change.)
--
You received this messa
Comment #3 on issue 988 by n.puttock: input/regresstion/quote-tie.ly :
missing note
http://code.google.com/p/lilypond/issues/detail?id=988
Sure, I'll tweak the texidoc to make it less ambiguous.
I'm not sure how often anybody would want to quote from two voices in direct
succession, but it c
Updates:
Status: Verified
Comment #2 on issue 985 by v.villenave: Noteheads don't merge when one of
the voices contains a second
http://code.google.com/p/lilypond/issues/detail?id=985
Sorry, closing.
--
You received this message because you are listed in the owner
or CC fields of thi
Comment #2 on issue 988 by percival.music.ca:
input/regresstion/quote-tie.ly : missing note
http://code.google.com/p/lilypond/issues/detail?id=988
Oh, I see. Sorry, I didn't realize what \cueDuring did.
Hmm. Could we change the text to "... This note should not be tied
to the 2nd visible n
Comment #4 on issue 987 by n.puttock: input/regression/quote-cyclic.ly :
some notes too small
http://code.google.com/p/lilypond/issues/detail?id=987
Sorry, I forgot to add the tag. :)
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you
Updates:
Labels: fixed_2_13_12
Comment #3 on issue 987 by percival.music.ca:
input/regression/quote-cyclic.ly : some notes too small
http://code.google.com/p/lilypond/issues/detail?id=987
Ok.
--
You received this message because you are listed in the owner
or CC fields of this issue,
Updates:
Status: Invalid
Comment #1 on issue 988 by n.puttock: input/regresstion/quote-tie.ly :
missing note
http://code.google.com/p/lilypond/issues/detail?id=988
There's nothing wrong with the regtest (apart from the lack of \new Voice
to correct
the size of the rests); if it brok
Updates:
Status: Fixed
Owner: n.puttock
Labels: -Regression
Comment #2 on issue 987 by n.puttock: input/regression/quote-cyclic.ly :
some notes too small
http://code.google.com/p/lilypond/issues/detail?id=987
This isn't a regression. It's an implicit voice problem: si
2010/1/20 Martin Straeten :
> in the current development version incipit-staves and main stave doesn't fit.
> See sample below:
> The alignment is ok with 2.12.2
Thank you for you bug report.
This is a known issue: the incipit snippets relied on a feature of the
old vertical spacing which is now
Comment #1 on issue 990 by percival.music.ca: automatically include
propert-init.ly in docs
http://code.google.com/p/lilypond/issues/detail?id=990
Issue 991 has been merged into this issue.
--
You received this message because you are listed in the owner
or CC fields of this issue, or becaus
Updates:
Status: Duplicate
Mergedinto: 990
Comment #1 on issue 991 by percival.music.ca: automatically include
propert-init.ly in docs
http://code.google.com/p/lilypond/issues/detail?id=991
grr, google code should disable the button for 5 seconds after being
clicked.
--
Yo
Status: Accepted
Owner:
Labels: Type-Build Priority-Postponed
New issue 991 by percival.music.ca: automatically include propert-init.ly
in docs
http://code.google.com/p/lilypond/issues/detail?id=991
It would be nice to include propert-init.ly in the documentation, maybe as
a Notation app
Status: Accepted
Owner:
Labels: Type-Build Priority-Postponed
New issue 990 by percival.music.ca: automatically include propert-init.ly
in docs
http://code.google.com/p/lilypond/issues/detail?id=990
It would be nice to include propert-init.ly in the documentation, maybe as
a Notation app
Status: Accepted
Owner:
Labels: Type-Documentation Priority-Critical
New issue 989 by percival.music.ca: ensure that no information is only in
the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
Some information can only be found in regtests... even worse, it's only
prese
Comment #1 on issue 986 by percival.music.ca: collision tuplet number and
partcombine text
http://code.google.com/p/lilypond/issues/detail?id=986
(No comment was entered for this change.)
Attachments:
foo.preview.png 2.9 KB
--
You received this message because you are listed in the
Comment #1 on issue 987 by percival.music.ca:
input/regression/quote-cyclic.ly : some notes too small
http://code.google.com/p/lilypond/issues/detail?id=987
Sorry, forgot the picture.
Attachments:
quote-cyclic.preview.png 3.3 KB
--
You received this message because you are listed i
Status: Accepted
Owner:
Labels: Type-Defect Priority-Critical Regression
New issue 988 by percival.music.ca: input/regresstion/quote-tie.ly :
missing note
http://code.google.com/p/lilypond/issues/detail?id=988
There's a missing note from cueI -- we should see an A in the second bar.
Al
On Wed, Jan 20, 2010 at 06:31:03PM +0200, Dmytro O. Redchuk wrote:
> In "quote-tie.ly":
>
> "Voices from different cues must not be tied together. In this example,
> the first note has a tie. This note should not be tied to the 2nd note."
>
> But there is no 2nd note, only 1st and 3rd.
I think t
Hmm... that would be nice, but we already have a bunch of bug
reports about collisions between note-heads and beams and the
like.
If you can find this example working in the 2.12 or 2.10 regtests,
I'll add it as Critical. If you find the example working in 2.8
or earlier, then I'll add it as Medi
Thanks, good catch. Added as
http://code.google.com/p/lilypond/issues/detail?id=987
Could you take a look at the 2.12 and 2.10 regtests? If this file
is in there, check if it's similarly broken. If it was working
in the 2.12 regtests, then adding that info to the issue tracker
would help the pr
Status: Accepted
Owner:
Labels: Type-Defect Priority-Critical Regression
New issue 987 by percival.music.ca: input/regression/quote-cyclic.ly : some
notes too small
http://code.google.com/p/lilypond/issues/detail?id=987
version 2.13.11
The second bar of notes in the B identifier should
Hi.
In "quote-tie.ly":
"Voices from different cues must not be tied together. In this example,
the first note has a tie. This note should not be tied to the 2nd note."
But there is no 2nd note, only 1st and 3rd.
So, i mean, this example seems to be constructed in a way which does not
allow to c
Hi.
"quote-during.ly": lower staff, last quarter, there is a collision
between "orig" and "quoted". Shouldn't it be resolved in some way?
Failed to find a bug report, again.
--
Dmytro O. Redchuk
LEGAL DISCLAIMER: This email was sent in hope in can help. If it is not,
feel free to ignore it or
Hi.
"quote-cyclic.ly": i guess lower voice should have normal note sizes in
the second measure.
(Sorry, i'm not sure, as always, and even more this time.)
--
Dmytro O. Redchuk
LEGAL DISCLAIMER: This email was sent in hope in can help. If it is not,
feel free to ignore it or send back any help
Hi, all,
in the attached example the tie positioning is not quite what I'd expect
to be the favourite option (on 2.13.11).
It's about chords with large intervals in between, where the tie can be
fitted into the space between note heads. This looks strange when the
inner ties exceed the ran
Status: Accepted
Owner:
Labels: Type-Collision Priority-High
New issue 986 by percival.music.ca: collision tuplet number and partcombine
text
http://code.google.com/p/lilypond/issues/detail?id=986
%%% note that the normal text ^"fo" does not collide.
%%% this appears in the part-comb
Updates:
Owner: ---
Mergedinto: 307
Comment #3 on issue 596 by percival.music.ca: collision tuplet number and
slur
http://code.google.com/p/lilypond/issues/detail?id=596
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
On Wed, Jan 20, 2010 at 10:06 AM, Dmytro O. Redchuk
wrote:
> "part-combine-text.ly": The part combiner detects a2, solo1 and solo2,
> and prints texts accordingly.
>
> Markup text says "expect: solo 2" (see below), but there is "Solo II"
> actually in the picture. I'd say something should be corre
Comment #3 on issue 307 by percival.music.ca: collision slur with tuplet
bracket
http://code.google.com/p/lilypond/issues/detail?id=307
Issue 596 has been merged into this issue.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starr
Hmm... ok, added as
http://code.google.com/p/lilypond/issues/detail?id=986
That said, I would be surprised if the regtest was always broken in
this way. Could somebody check previous regtests and let me know if
you find it working?
Cheers,
- Graham
On Wed, Jan 20, 2010 at 11:01 AM, Trevor Danie
Updates:
Status: Duplicate
Comment #2 on issue 596 by percival.music.ca: collision tuplet number and
slur
http://code.google.com/p/lilypond/issues/detail?id=596
Dupe of 307
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you sta
Could one of the bug meisters finally get around to verifying fixed
issues? I don't mind if you leave out the issues about GUB (since you
can't really verify those), but there's still a ton of things you
*could* be verifying.
Cheers,
- Graham
___
bug-
> I'm not top posting.
Hi,
in the current development version incipit-staves and main stave doesn't fit.
See sample below:
The alignment is ok with 2.12.2
best regards, Martin
%% misaligned incipits for clefs exceeding staff-lines
\version "2.13.11"
\paper{ ragged-right=##t }
incipitClef =
#(d
Dmytro O. Redchuk wrote Wednesday, January 20, 2010 10:13 AM
In "part-combine-tuplet-end.ly": there is a collision between
tuplet
digit and partcombine text. I've failed to find a bug report for
this
issue, that's why i'm writing.
There are so many problems with part-combine that I think
p
Hi.
Possibly, not directly related to regtests...
In "part-combine-tuplet-end.ly": there is a collision between tuplet
digit and partcombine text. I've failed to find a bug report for this
issue, that's why i'm writing.
--
Dmytro O. Redchuk
LEGAL DISCLAIMER: This email was sent in hope in can
Hi.
"part-combine-text.ly": The part combiner detects a2, solo1 and solo2,
and prints texts accordingly.
Markup text says "expect: solo 2" (see below), but there is "Solo II"
actually in the picture. I'd say something should be corrected (markup
text is quite right regarding "a2", so...)
% -
Comment #8 on issue 969 by fodber: find a tool to convert SVG->EPS
http://code.google.com/p/lilypond/issues/detail?id=969
Batik http://xmlgraphics.apache.org/batik/tools/rasterizer.html can be
easily used to
convert SVG to PNG.
--
You received this message because you are listed in the owne
40 matches
Mail list logo
