> current: "Hyphens are print at the ..." should read "Hyphens are
> printed at the..."
Stan, you are producing many valid bug reports. Can you try the GNU
diff program to simplify the task of merging your fixes into the
source? For example, you save the original file to `foo.orig', and
the fi
On Sun, 06 Jan 2008 09:10:39 +0100 (CET)
Werner LEMBERG <[EMAIL PROTECTED]> wrote:
> > current: "Hyphens are print at the ..." should read "Hyphens are
> > printed at the..."
>
> Stan, you are producing many valid bug reports. Can you try the GNU
> diff program to simplify the task of merging
Hi Valentin,
Valentin Villenave wrote:
> Thank you for the report (took me a few minutes to understand what it
> was all about; as a pianist I don't use the \transposition command
> very often ;)
This is the first time for me too (I normally write choir music). :-) I was
wondering why I cannot g
Issue 548: \transposition produces different pitches depending on the
notenames language
http://code.google.com/p/lilypond/issues/detail?id=548
Comment #1 by rzedeler:
This is not a bug.
bb and heses are Finnish for b DOUBLE flat. NOT b flat.
What you are looking for is \transposition b
b is Fin
Risto Vääräniemi skrev:
I was
wondering why I cannot get the right tune out of my speakers and when I
removed the \transposition altogether and used the \transpose command in the
MIDI section the revelation came to me.
This is not a bug.
See my comment in the bug tracker.
One small addition t
Dear Rune and all,
Rune Zedeler wrote:
> This is not a bug.
> See my comment in the bug tracker.
Arrgh! Stupid, stupid me. My mind got messed up by all the different pitch
names. With "\transposition b" it works.
Thanks and sorry for the trouble.
-Risto
--
View this message in context:
http:
Issue 546: Incorrect merging when a same note has different accidentals
http://code.google.com/p/lilypond/issues/detail?id=546
Comment #4 by rzedeler:
This is a known limitation of Lilypond. It is mentioned at the bottom of
http://lilypond.org/doc/v2.11/Documentation/user/lilypond/Collision-resol
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 #2 by rzedeler:
Cf. #247 this is not supported. The bug is not that we get a collision.
The bug is
that we do not get an error message.
Issue att
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 #3 by rzedeler:
Sorry. Meant cf. #546
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you
Issue 546: Incorrect merging when a same note has different accidentals
http://code.google.com/p/lilypond/issues/detail?id=546
Comment #5 by v.villenave:
The doc says "in a chord". I'll just add "...or a polyphonic situation" then.
Thanks
--
You received this message because you are listed in
I could not reproduce the problem with a small example, so I'm
giving the full file, since it is for a short piece anyway.
The upbeat formatting is wrong. As you can see, the space between
the leading 2 8ths is too large: it should be the same as the
other 8ths in the piece.
Raphael
\version "2.
In the presence of the leading appogiatura, there are two repeat
bars output at the beginning, whereas there should be only one.
The second one (after the appogiatura note) is the one that should
not be there.
Raphael
% Extra repeat bar
\version "2.11.37"
Up = \relative c'' {
\partial 4 a8 g |
\
2008/1/5, Valentin Villenave <[EMAIL PROTECTED]>:
> 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.
Please contact the author of t
Issue 551: input/regression/glissando.ly
http://code.google.com/p/lilypond/issues/detail?id=551
Comment #1 by hanwenn:
Hi,
the trickery refers to the C++ code. If you have a look at the
glissando_engraver,
you will know what I mean.
Can you guys please exercise some restraint before throwing a
Issue 549: input/regression/slur-script.ly
http://code.google.com/p/lilypond/issues/detail?id=549
Comment #1 by hanwenn:
can we stop marking possibly outdated regtests as being
priority-regression? These
are not regression bugs, if they are bugs at all.
--
You received this message because y
Issue 551: input/regression/glissando.ly
http://code.google.com/p/lilypond/issues/detail?id=551
Comment #2 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Labels: -Priority-Regression Priority-Low
--
You received this message because you are listed in the
Issue 549: input/regression/slur-script.ly
http://code.google.com/p/lilypond/issues/detail?id=549
Comment #2 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Labels: -Priority-Regression Priority-Low
--
You received this message because you are listed in t
Issue 536: font error in win32 in 2.11.36
http://code.google.com/p/lilypond/issues/detail?id=536
Comment #2 by hanwenn:
should be fixed .37
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue
2008/1/6, Han-Wen Nienhuys <[EMAIL PROTECTED]>:
> Please contact the author of the festival stuff about this.
Done. I wrote him a long nice mail :)
Quite an interesting project, by the way.
> I have made a mistake, as the file was committed without a texidoc
> header, but it may test valuable
Issue 551: input/regression/glissando.ly
http://code.google.com/p/lilypond/issues/detail?id=551
Comment #3 by gpermus:
The only test I removed was
grace-nest.ly
because diff showed that it was identical to
grace-nest1.ly
other than whitespace.
--
You received this message because you are lis
Issue 518: \oldaddlyrics broken
http://code.google.com/p/lilypond/issues/detail?id=518
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 issue,
Issue 549: input/regression/slur-script.ly
http://code.google.com/p/lilypond/issues/detail?id=549
Comment #3 by gpermus:
They're not "bugs", but they are "issues". I thought that issues with
the regtests
would qualify as priority-regression, but of course we'll follow your
instructions
about
Issue 519: PDF filesize has increased between 1.9.8 and 2.10
http://code.google.com/p/lilypond/issues/detail?id=519
Comment #4 by gpermus:
Sorry to nag, (and sorry for my ignorance about pdfs), but I can't
verify this as
closed yet.
- will PDFs created on windows look identical (on windows, os
Issue 504: lilypond broken on osx 10.5 x86
http://code.google.com/p/lilypond/issues/detail?id=504
Comment #35 by tinuviel874:
More info on using the command line PPC version:
When I do:
cd /Applictions/LilyPond.app/Contents/Resources/bin
./lilypond test.ly
it fails with an error message about
Issue 504: lilypond broken on osx 10.5 x86
http://code.google.com/p/lilypond/issues/detail?id=504
Comment #36 by tinuviel874:
More info on using the command line PPC version:
When I do:
cd /Applictions/LilyPond.app/Contents/Resources/bin
./lilypond test.ly
it fails with an error message about
Issue 519: PDF filesize has increased between 1.9.8 and 2.10
http://code.google.com/p/lilypond/issues/detail?id=519
Comment #5 by v.villenave:
That's because you do not use Windows :)
When I was still using Sibelius, the PDF I produced couldn't be read on
any standard
computer (i.e. without the
Issue 549: input/regression/slur-script.ly
http://code.google.com/p/lilypond/issues/detail?id=549
Comment #4 by v.villenave:
My initial intention was to open a single issue named "regtests
modernization", or
something, and mark them as Enhancement-Low priority (since they are currently
working,
Issue 527: segfault in bad input
http://code.google.com/p/lilypond/issues/detail?id=527
Comment #3 by v.villenave:
(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 i
Issue 537: ambitus incorrect upper pitch
http://code.google.com/p/lilypond/issues/detail?id=537
Comment #5 by v.villenave:
Works like a charm now.
Issue attribute updates:
Status: Verified
--
You received this message because you are listed in the owner
or CC fields of this issue, or b
Issue 548: \transposition produces different pitches depending on the
notenames language
http://code.google.com/p/lilypond/issues/detail?id=548
Comment #2 by v.villenave:
Oh yes! I missed it because suomi.ly is not yet documented in French
(should have
looked at the English doc).
Issue attri
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 #4 by v.villenave:
OK, let's just keep #546 as an Enhancement request and discard this one.
Issue attribute updates:
Status: Verified
--
Yo
Issue 519: PDF filesize has increased between 1.9.8 and 2.10
http://code.google.com/p/lilypond/issues/detail?id=519
Comment #6 by gpermus:
"... **IF** the linux-created PDFs **don't** include the font".
(emphasis added)
Can I produce a pdf on linux, and have it viewed on windows? I'm
guessing
32 matches
Mail list logo
