I don't want to get too bogged down trying to explain the
regtests, since the developers know what they mean, and they're
the only ones who look at them... but I think this improvement is
worth doing, so I've applied it.
Thanks,
- Graham
On Sun, 6 Jan 2008 07:45:44 +0100
Wilbert Berendsen <[EMAIL
Op zaterdag 5 januari 2008, schreef Stan Sanderson:
> regressions: combine-switch-voice-2.ly -- typo
>
> current: texidoc = "switching voices halfway a lyricsto is possible."
> suggested: texidoc = "switching voices halfway with lyricsto is
> possible."
with "a lyricsto" is meant "a block of lyric
Issue 551: input/regression/glissando.ly
http://code.google.com/p/lilypond/issues/detail?id=551
New issue report by gpermus:
% Nobody is really certain what to do about this example, but clearly
% something needs to be clarified. -gp
Valentin / Stan discussion:
2008/1/5, Stan Sanderson <[EMAI
I think this is fine; when I move the text higher, it obscures the
stem. For whatever reason, I think 2.11.37 automatically places
the text lower down than it did previously.
Thanks for all this checking.
Cheers,
- Graham
On Sat, 5 Jan 2008 10:06:34 -0600
Stan Sanderson <[EMAIL PROTECTED]> wrot
Issue 550: input/regression/page-turn-page-breaking-auto-first-page.ly
http://code.google.com/p/lilypond/issues/detail?id=550
New issue report by gpermus:
% possibly deprecated regtest based on recent page breaking work.
% Joe: should we just delete this regtest, or do you want to modify
% it in
Issue 549: input/regression/slur-script.ly
http://code.google.com/p/lilypond/issues/detail?id=549
New issue report by gpermus:
% I think this has been deprecated by the vertical skyline stuff.
% shall we delete this regtest?
slur-script.ly - v2.11.37 handles slurs as described by
the text withou
On Sun, 6 Jan 2008 01:58:40 +0100
"Valentin Villenave" <[EMAIL PROTECTED]> wrote:
> 2008/1/6, Stan Sanderson <[EMAIL PROTECTED]>:
> > regressions: midi-volume-equaliser.ly -- typo
>
> OK, here's a patch accordingly to your last proposals. graham, can you
> commit it please?
Done.
Cheers,
- Gra
On Sun, 6 Jan 2008 00:15:46 +0100
"Valentin Villenave" <[EMAIL PROTECTED]> wrote:
> 2008/1/5, Stan Sanderson <[EMAIL PROTECTED]>:
> > regressions: song-reordering.ly : is this test a duplicate of song-
> > reordering2.ly ?
>
> I think so.
>
> I decided to remove it, as it was obviously a duplica
2008/1/5, Stan Sanderson <[EMAIL PROTECTED]>:
> While the snippet renders correctly when I compile it, the image
> rendered in the regression/collated-files document (using Firefox
> 2.0.0.11, Mac OS 10.4.11, PPC) is incorrect. The third tuplet bracket
> (for the tuplet crossing three staves) is no
2008/1/5, Risto Vääräniemi <[EMAIL PROTECTED]>:
> The example below shows the effects. If you comment out the \include line
> and use the "bes" option you get a unison sound. If you use either "bb" or
> "heses" with the \include you get some exotic tunes. :-)
Thank you for the report (took me a f
Issue 548: \transposition produces different pitches depending on the
notenames language
http://code.google.com/p/lilypond/issues/detail?id=548
New issue report by v.villenave:
%{
The only way to make this snippet work as expected
-- i.e. the two parts sound as a unison --
is to write it using
2008/1/6, Stan Sanderson <[EMAIL PROTECTED]>:
> regressions: midi-volume-equaliser.ly -- typo
OK, here's a patch accordingly to your last proposals. graham, can you
commit it please?
Cheers,
Valentin
diff --git a/input/regression/finger-chords-accidental.ly b/input/regression/finger-chords-accid
Issue 547: Accidentals collide when added to a same note in a
polyphonic situation
http://code.google.com/p/lilypond/issues/detail?id=547
Comment #1 by v.villenave:
This might be related to #546 (in the same output, the two notes should
not be merged
since they have different pitches).
--
Y
Issue 547: Accidentals collide when added to a same note in a
polyphonic situation
http://code.google.com/p/lilypond/issues/detail?id=547
New issue report by v.villenave:
% See attached picture
\version "2.11.34"
<< {aes'8} \\ {ais'} >>
Attachments:
collision.png 3.4 KB
Issue attri
Issue 546: Incorrect merging when a same note has different accidentals
http://code.google.com/p/lilypond/issues/detail?id=546
Comment #3 by gpermus:
Exactly. I don't think it's useful for you or I to speculate as to
whether one piece
of code is causing both errors -- I know that *I* certainly
Issue 546: Incorrect merging when a same note has different accidentals
http://code.google.com/p/lilypond/issues/detail?id=546
Comment #2 by v.villenave:
Yes, I had initally marked it as Medium-priority... but I just found it
too horrible :)
As I told Trevor on the bug list, this looks like tw
Issue 546: Incorrect merging when a same note has different accidentals
http://code.google.com/p/lilypond/issues/detail?id=546
Comment #1 by gpermus:
- it's not High. High is for things like segfaults. Unless you see
otherwise in the
regtests, it's not even a regression.
- What is the (singu
2008/1/5, Trevor Daniels <[EMAIL PROTECTED]>:
> Here's your first bug:
Yeepee! :)
> \version "2.11.34"
> % These two notes are different and should not be merged
> << {aes'8} \\ {a'} >>
> << {aes'8} \\ {a'?} >>
Oh yes! This is absolutely awful!
I added a sharp somewhere to emphasize the collis
Issue 546: Incorrect merging when a same note has different accidentals
http://code.google.com/p/lilypond/issues/detail?id=546
New issue report by v.villenave:
% These notes should not be merged;
% besides, the accidentals collide with each other.
<< {aes'8} \\ {ais'} >>
<< {aes'8} \\ {a'?}>>
regressions: midi-volume-equaliser.ly -- typo
Suggest changing from "The full orchestra plays a notes, where..." to
"The full orchestra plays a note, where..."
Stan
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman
regressions: lyric-hyphen-retain.ly -- typo
suggest changing "The minimum distance between lyrics are
determined..." to
"The minimum distance between lyrics is determined..."
Stan
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.
2008/1/5, Stan Sanderson <[EMAIL PROTECTED]>:
> regressions: song-reordering.ly : is this test a duplicate of song-
> reordering2.ly ?
I think so.
I decided to remove it, as it was obviously a duplicate.
Thank you for all this work; Graham, here's a patch for all typo
errors that Stan has been h
regressions: lyric-hyphen-break.ly -- typo "...print..."
current: "Hyphens are print at the ..." should read "Hyphens are
printed at the..."
Stan
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypo
regressions: combine-switch-voice-2.ly -- typo
current: texidoc = "switching voices halfway a lyricsto is possible."
suggested: texidoc = "switching voices halfway with lyricsto is
possible."
Stan
___
bug-lilypond mailing list
bug-lilypond@gnu
Hi Valentin
Here's your first bug:
\version "2.11.34"
% These two notes are different and should not be merged
<< {aes'8} \\ {a'} >>
<< {aes'8} \\ {a'?} >>
Trevor D
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/li
regressions: tuplet-bracket-cross-staff.ly - strange rendering
While the snippet renders correctly when I compile it, the image
rendered in the regression/collated-files document (using Firefox
2.0.0.11, Mac OS 10.4.11, PPC) is incorrect. The third tuplet bracket
(for the tuplet crossing th
regressions: tie-grace.ly - text error
Text reads, "Tieing a grace to the to a following..."
1. Spelling: Tying rather than Tieing
2. omit "the to"
Corrected: "Tying a grace to a following grace or main note works."
Stan
___
bug-lilypond mailin
Dear All,
I was writing a piece of score with transposed instruments and found out
that the \transposition command does not work in all cases. With B-flat
instruments it expects a parameter "bes" which is not present in Finnish
language file "suomi.ly". In Finnish you use either "bb" or "heses" f
Thanks, fixed.
Cheers,
- Graham
On Fri, 4 Jan 2008 20:30:05 -0600
Stan Sanderson <[EMAIL PROTECTED]> wrote:
> hairpin-dashed.ly test appears to fail. No dashed hairpins are
> rendered.
>
>
>
> Stan
>
>
>
>
> ___
> bug-lilypond mailing list
> bug
On Sat, 5 Jan 2008 16:41:35 +0100
"Valentin Villenave" <[EMAIL PROTECTED]> wrote:
> 2008/1/5, Stan Sanderson <[EMAIL PROTECTED]>:
> > regression: grace-nest.ly and grace-nest1.ly appear to be
> > essentially identical. grace-nest2.ly seems to be a complete test.
grace-nest.ly has been deleted; t
regressions: spacing-section.ly (text correction)
Text reads: "New sections for spacing can be started with
ewSpacingSection. In this ..."
I assume the "n" is missing from new due to the inclusion of "\" in
the @code{\newSpacingSection} .
Stan
_
regressions: song-reordering.ly : is this test a duplicate of song-
reordering2.ly ?
There is no descriptive text and, although the two snippets differ in
the order of voiceOne and voiceTwo definitions, the output appears to
be identical in the two tests.
Stan
_
regressions: slur-script.ly - v2.11.37 handles slurs as described by
the text without needing the following overrides included in the test
snippet:
\override DynamicLineSpanner #'avoid-slur = #'outside
\override DynamicLineSpanner #'avoid-slur = #'around
\override DynamicLineSpanner #'avoi
regressions: page-turn-page-breaking-auto-first-page.ly
confusion? Text suggests the page number should be 2 due to music not
fitting on a single page. However, the music is on one page, although
it is very tight, and the page number is 1.
Text excerpt: "In this example, auto-first-page-num
regressions: whiteout.ly - broken in v2.11.37, was working in 2.11.36.
Stem is visible; it was covered in 2.11.36.
Stan
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
2008/1/5, Stan Sanderson <[EMAIL PROTECTED]>:
> regression: grace-nest.ly and grace-nest1.ly appear to be essentially
> identical. grace-nest2.ly seems to be a complete test.
>
> Also, I believe the text should read, "...sequential music..." rather
> than "...sequential musics..." .
I don't know
2008/1/5, Stan Sanderson <[EMAIL PROTECTED]>:
> regressions: glissando.ly text reads, "The engraver does no time-
> keeping, so it involves some trickery to get << { s8 s8 s4 } { c4
> \gliss d4 } >> working correctly."
I think this is totally deprecated.
First of all, the \gliss syntax mentioned i
37 matches
Mail list logo
