wrong position of rhythmic dots

I wonder whether a patch similar to * lily/stem.cc (position_noteheads): rounding error robustness. (from 2004-01-25) can fix the problem with incorrectly positioned rhythmic dots -- you told me that you can't repeat the problem. Werner ==

rest problem (revisited)

Since you plan to consolidate LilyPond for the next stable release, I will check my collection of bugs, reporting problems. The bugs below are rating very high on my wishlist. Werner == % % This file shows a problem with

Re: build warnings

> > The very first message of the build process is repeated very often. > > fixed in CVS. Thanks! There is just one warning remaining which appears repeatedly during `make install', e.g. make[2]: Leaving directory `lilypond/stepmake' install-info --info-dir=/usr/local/info ./out/lilypond.i

Re: Rectangle around the note head

On Sunday March 21 2004 10:31, Matevz Jekovec wrote: > Edward Sanford Sutton, III wrote: > >On Friday March 19 2004 15:25, Matevz Jekovec wrote: > >>I was searching the documentation a bit for a feature which draws a > >>rectangle around the certain note head (or streched around 2 notes when > >>pu

lilypond-devel for the gentooist :

I correct my previous post, in case it could help someone : Just add : sys-apps/texinfo ~x86 In your /etc/portage/package.keywords and emerge -a sys-apps/keywords That's it ! PS : unfortunatly, mftrace is still 1.0.19 in the portage tree, go for it by hand... -- Olivier <[EMAIL PROTECTED]>

Re : Lilypond 2.1.32 released

That was it. It seems that this is a problem of my hown system, I ask other gentooist on the web, the texinfo stable version should be the 4.6. Thank's Némo. -- Olivier <[EMAIL PROTECTED]> Le 21.03.2004 14:24:49, Han-Wen Nienhuys a écrit : [EMAIL PROTECTED] writes: > > I saw few days ago so

python warnings

[EMAIL PROTECTED] writes: > > [CVS 2004-03-20 13:43 MET] > > I get the following harmless warnings, using python 2.3.3: > > mf-to-table.py:55: FutureWarning: > x< in Python 2.4 and up > cs = cs + (ord (b) << shift) > mf-to-table.py:280: FutureWarning: > %u/%o/%x/%X of nega

wrong size of time signatures

[EMAIL PROTECTED] writes: > > [CVS 2004-03-20 13:43 MET] > > Look at the attached image: The 3/4 sign is too small. It is taken > from a staff reduced in size with > > fontSize = #-4 > \override StaffSymbol #'staff-space = #(magstep -4) > > This is a severe bug. fixed in cvs. -- Han-W

build warnings

[EMAIL PROTECTED] writes: > > Unfortunately, the lilypond build system exceeds the complexness of > both groff and Freetype by some orders of magnitude -- and both are > already quite complicated. Were it easier to understand I would try > to fix it by myself... > > The very first message of the

build warnings

Unfortunately, the lilypond build system exceeds the complexness of both groff and Freetype by some orders of magnitude -- and both are already quite complicated. Were it easier to understand I would try to fix it by myself... The very first message of the build process is repeated very often. A

wrong size of time signatures

[CVS 2004-03-20 13:43 MET] Look at the attached image: The 3/4 sign is too small. It is taken from a staff reduced in size with fontSize = #-4 \override StaffSymbol #'staff-space = #(magstep -4) This is a severe bug. Werner <>___ Lilypond-d

install-info problems

[texinfo CVS 2004-02-28 05:36 MET] [lilypond CVS 2004-03-20 13:43 MET] I have (among other entries) the following in my /usr/local/info/dir file: == GNU music project * GNU LilyPond: (lilypond/lilypond). The GNU musi

python warnings

[CVS 2004-03-20 13:43 MET] I get the following harmless warnings, using python 2.3.3: mf-to-table.py:55: FutureWarning: x

Re: info problems

[lilypond CVS 2004-03-20 13:43 MET] [texinfo CVS 2004-02-28 05:36 MET] > >> > I get e.g. `Easier Music Entry: No such file or directory'. > >> > > >> > So there are many dead links. Probably a bug in `info'? > >> > >> Probably someone needs/needen to run texinfo-all-menu-update. Is > >> this fi

Re : Lilypond 2.1.32 released

[EMAIL PROTECTED] writes: > > I saw few days ago someone else pointing this problem for lily 2.1.31 > and it look like it was fixed on cvs (I don't tried it). But it's still > broken for me. > > I'm under gentoo 1.4, python 2.3.3, guile 1.6.4. If you need other > informations, tell me. mak

Re: anomalies with 2.1.32

On Sun, 2004-03-21 at 12:28, Han-Wen Nienhuys wrote: > [EMAIL PROTECTED] writes: > > I'm having similar trouble reproducing the oddities with smaller files. > > Most of the really strange things I was having have disappeared as of > > ChangLog 1.1917; I'm not seeing the disembodied beams etc, in t

Re: anomalies with 2.1.32

[EMAIL PROTECTED] writes: > I'm having similar trouble reproducing the oddities with smaller files. > Most of the really strange things I was having have disappeared as of > ChangLog 1.1917; I'm not seeing the disembodied beams etc, in that file > of mine. I am, however, still having some strang

Re: anomalies with 2.1.32

On Sun, 2004-03-21 at 11:42, Matthias Kilian wrote: > [Changed to development list, since it's really a bleeding-edge issue] > > On Sat, Mar 20, 2004 at 04:43:34PM +, David Bobroff wrote: > > I'm still getting those same anomalies with v2.1.32; that is, dismbodied > > beams, multimeasure rest

Re: anomalies with 2.1.32

[Changed to development list, since it's really a bleeding-edge issue] On Sat, Mar 20, 2004 at 04:43:34PM +, David Bobroff wrote: > I'm still getting those same anomalies with v2.1.32; that is, dismbodied > beams, multimeasure rest numbers displaced to the right, etc. [...] Me, too :-( For e