Updates:
Status: Started
Comment #4 on issue 764 by gpermus: convert-ly does not work in the lilypad
for OSX 10.4
http://code.google.com/p/lilypond/issues/detail?id=764
2.13.3 fixes the GUI, but I believe the fix for convert-ly didn't make it
in. 2.13.4
will include this, if I ever
Comment #3 on issue 764 by jameselihubailey: convert-ly does not work in
the lilypad for OSX 10.4
http://code.google.com/p/lilypond/issues/detail?id=764
Oh, I just had a thought, are you testing with 2.13.3? I think that fixes
this issue.
--
You received this message because you are liste
In certain cases, the combination of tabstaff with chords-mode seems to cause
serious spacing problems. Look at this example
http://hjg.com.ar/varios/lilypondb1/test2.png
(extra spacing above am6 chord in third measure, and above the last chord in
last measure)
The source code is here:
http://hj
On Wed, Jul 15, 2009 at 05:40:24PM +0200, Valentin Villenave wrote:
> Porting LilyPond to Mac OS 10.5 has been really painful for the past
> couple of years (we recently had a breakthrough, but it's not
> officially implemented yet).
It's included in 2.13.3.
Cheers,
- Graham
___
2009/7/15 Valentin Villenave :
> 2009/5/15 Francisco Vila :
>> When the staff size is set down to 17, a possible bug makes grace
>> notes to suddenly have very long stems. At a size of 18 the problem is
>> not shown.
>
> Hi Francisco (and my apologies for the delay),
> your report has been added as
2009/6/6 Kjell :
> I attempted to follow instruction set C for LilyPond & Terminal install on Mac
> OS X Leopard. I've run into problems.
[...]
> So what's going on? Please assist.
Greetings, and sorry for the delay.
Porting LilyPond to Mac OS 10.5 has been really painful for the past
couple of y
2009/6/5 Werner LEMBERG :
> There is an explicit call to AC_LANG_C in the top-level `configure.in'
> file, which should be removed IMHO. Ideally, everything should be run
> with C++ (we only use g++), and the AC_LANG_PUSH/POP trickery -- `also
> in aclocal.m4' -- should be removed, too.
Although
Status: Started
Owner: v.villenave
Labels: Type-Defect Priority-Low Maintainability
New issue 805 by v.villenave: Irrelevant configure message with autoconf
and gettext test
http://code.google.com/p/lilypond/issues/detail?id=805
As Werner has pointed out, we're currently missing a proper test
Status: Accepted
Owner: v.villenave
Labels: Type-Enhancement Maintainability Priority-Low
New issue 804 by v.villenave: Code cleaning: checking types-conversion
issues
http://code.google.com/p/lilypond/issues/detail?id=804
Compiling LilyPond with a recent GCC produces many warnings such as:
2009/6/4 Joe Neeman :
> On Mon, 2009-06-01 at 12:22 +0200, Werner LEMBERG wrote:
>> Most of them, I presume, are harmless, but... I think it would be a
>> good idea to fix them.
>
> Perhaps this would be a good job for our new Code Janitor? There are
> some places (particularly ttf.cc) where it co
2009/6/3 Francisco Vila :
> Could you send a test file for which convert -ly gives this output so
> I can try it with the various locales?
Although this should be a trivial thing to fix, it seems that it has
gone forgotten. I have added it to the tracker as #803, hoping that
someone with enough ti
Status: Accepted
Owner: v.villenave
CC: lemzwerg
Labels: Type-Documentation Priority-Low Warning-nitpick
New issue 803 by v.villenave: correction needed for the German translation
of convert-ly
http://code.google.com/p/lilypond/issues/detail?id=803
As Werner explained, the translated NOT_SMAR
Updates:
Status: Duplicate
Mergedinto: 774
Comment #1 on issue 802 by v.villenave: Trill spanners should begin at the
same place, regardless of the staff size
http://code.google.com/p/lilypond/issues/detail?id=802
Gosh, I should have seen that one. Duplicate of issue 774.
--
2009/6/2 Vivian Barty-Taylor :
> I can't get the SeparationItem spacing tweak to work in 2.12.2 (on OSX). See
> code and attached PNG. Is this a known issue or is there an alternative
> workaround?
Greetings Vivian, and sorry for the delay.
As you may have noticed, this has been fixed in the 2.13
Updates:
Cc: lemzwerg
Comment #1 on issue 774 by v.villenave: wrong horizontal trill position in
small staff lines
http://code.google.com/p/lilypond/issues/detail?id=774
Issue 802 has been merged into this issue.
--
You received this message because you are listed in the owner
or CC
2009/7/15 Valentin Villenave :
> Now added as #802.
Oh, I see you've taken care of it. Marked as duplicate and closed,
sorry for the noise.
Regards,
Valentin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-
2009/6/1 Werner LEMBERG :
> The horizontal position of the beginning of a trill spanner must be
> positioned correctly relative to the note head it is attached to, even if
> scaled to a smaller size.
Thank you Werner, and sorry for the delay.
Now added as #802.
Regards,
Valentin
___
Status: Accepted
Owner: v.villenave
CC: lemzwerg
Labels: Type-Defect Priority-Medium Engraving-nitpick
New issue 802 by v.villenave: Trill spanners should begin at the same
place, regardless of the staff size
http://code.google.com/p/lilypond/issues/detail?id=802
% new report from Werner:
\h
2009/5/29 ArnoWaschk :
> results in the augmentation dot printed "behind" the accidental.
> Both in 2.12 an 2.13 on this machine.
Although this looks very familiar, I couldn't find the exact same bug
in our tracker. So this is now know as
http://code.google.com/p/lilypond/issues/detail?id=801.
Re
Status: Accepted
Owner: v.villenave
Labels: Type-Collision Priority-Medium
New issue 801 by v.villenave: Accidentals in a chord may collide with
augmentation dots
http://code.google.com/p/lilypond/issues/detail?id=801
% In the following example, the dot collides with the accidental
% from the
Le 15 juil. 09 à 16:22, Valentin Villenave a écrit :
2009/5/22 Nicolas Sceaux :
In case of multiple vocal staves, __ extender lines in melisma may be
broken,
Master Nicolas Sceaux,
Your humble servant is deeply confused for unforgettably having let
Your bug report unprocessed. May the fact t
2009/5/22 Nicolas Sceaux :
> In case of multiple vocal staves, __ extender lines in melisma may be
> broken,
Master Nicolas Sceaux,
Your humble servant is deeply confused for unforgettably having let
Your bug report unprocessed. May the fact that, as a mere
compensation, Your report has been attr
Status: Accepted
Owner: v.villenave
CC: nicolas.sceaux
Labels: Type-Defect Priority-Medium
New issue 800 by v.villenave: Melismas extenders are broken when there's
another staff
http://code.google.com/p/lilypond/issues/detail?id=800
% New report from Nicolas Sceaux:
%{
In case of multiple vo
The best place to start is the documentation. Go to:
http://lilypond.org/web/
Select a version under "Quick Links" and go to the documentation. Then
go to the "Learning Manual." Quick tip; LilyPond will not start up with
a blank page. There is no GUI. It is a batch program which operates
Hi,
I got Lily pond a long time ago but have never used it before.
I can understand the manual but I can't start writing! What do I need to do to
see a blank page?
I'm sure this looks stupid!
Thanks.
With best wishes,
Kirk
___
bug-lilypond mail
Hello. I tried installing lilypond tonight on my iMac, OS v. 10.5.7. I am an
experienced TexShop user.
I created the lilypond.engine file for bash in TeXShop (you should say this text
file needs a .engine extension) and moved it into the TeXShop engine directory.
Then I did chmod +x on the file fr
2009/5/15 Francisco Vila :
> When the staff size is set down to 17, a possible bug makes grace
> notes to suddenly have very long stems. At a size of 18 the problem is
> not shown.
Hi Francisco (and my apologies for the delay),
your report has been added as issue #799.
Regards,
Valentin
___
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Low Engraving-nitpick
New issue 799 by v.villenave: Weird grace notes' stems length depending on
the staff size
http://code.google.com/p/lilypond/issues/detail?id=799
New report from Francisco:
When the staff size is set down t
2009/5/11 Mark Polesky :
> If different stem lengths for the same note bothers
> you, realize that the complexities of typesetting
> beams demand that stem lengths vary, often greatly.
Although I can't say I've understood all of this interesting (albeit
technical) discussion, it seems that the sub
Status: Accepted
Owner: v.villenave
Labels: Type-Enhancement Priority-Postponed Engraving-nitpick
New issue 798 by v.villenave: Enhancement: possible improvements to the
stem-length algorithm
http://code.google.com/p/lilypond/issues/detail?id=798
In a very documented discussion, Pekka Siponen
Comment #1 on issue 797 by v.villenave: Enhancement: numbers in chord names
should have their own font
http://code.google.com/p/lilypond/issues/detail?id=797
Please also have a look at
http://lists.gnu.org/archive/html/lilypond-user/2009-04/msg00835.html
--
You received this message because
2009/5/9 Pekka Siponen :
>
> 1. The chord suffixes should not be scaled (see attachment). The
> weight of the smaller character gets too light if it is simply scaled
> down from the original font. A correctly weighed glyph is needed.
Thanks Pekka, this has now been added as an enhancement request
Status: Accepted
Owner: v.villenave
Labels: Type-Enhancement Priority-Postponed Engraving-nitpick
New issue 797 by v.villenave: Enhancement: numbers in chord names should
have their own font
http://code.google.com/p/lilypond/issues/detail?id=797
Here are some suggestions that Pekka Siponen ma
Updates:
Status: Verified
Comment #17 on issue 546 by v.villenave: Incorrect merging when a same note
has different accidentals
http://code.google.com/p/lilypond/issues/detail?id=546
I'm happy to close this issue. Many thanks to Erlend and Joe.
--
You received this message because yo
2009/4/26 Marc Mouries :
> % the slur collides with the natural symbol ♮
Though I'm sure I've seen such a thing before, I couldn't find it. So,
here it is:
http://code.google.com/p/lilypond/issues/detail?id=796
Regards,
Valentin
___
bug-lilypond maili
Status: Accepted
Owner: v.villenave
Labels: Type-Collision Priority-Medium
New issue 796 by v.villenave: Slurs should not collide with accidentals
http://code.google.com/p/lilypond/issues/detail?id=796
% This may be related to issue 76 or issue 480.
\version "2.13.3" % has never worked AFAICR.
Status: Accepted
Owner: v.villenave
Labels: Type-Collision Priority-Medium
New issue 795 by v.villenave: Beams do not take grace notes into account
http://code.google.com/p/lilypond/issues/detail?id=795
% Yet another problem with grace notes (possibly duplicate):
\version "2.13.3" % This has ne
2009/4/26 Marc Mouries :
> % the stem of the acciaccatura collides with the beam
Thanks Marc, added as:
http://code.google.com/p/lilypond/issues/detail?id=795
Regards,
Valentin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/ma
38 matches
Mail list logo
