Pedro Kröger wrote:
Thomas Bushnell BSG <[EMAIL PROTECTED]> writes:
Ok, adoption in progress.
that's very good to hear! it's nice to know that debian will have
up-to-date lilypond versions again.
Yes!!
Please consider my request to rename the existing lilypond-snapshot
packages to pl
[sorry If I took too long to answer this, it's the beginning of the
semester over here (I'm a teacher) and I've been preparing classes and
expending more time in the classroom than in front of the
computer. plus, I'm finishing a big concerto for percussion and
orchestra that is taking lots of my t
Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes:
>>> We are a bit concerned with old LilyPond packages, and a potential
>>> new maintainer (Pedro Kroger) with his sponsor going mia.
>>
>> Who was going to sponsor him?
>
> I don't think Pedro told me that. Pedro?
actually he was going to sponsor anot
> The downstroke of change clef becomes thinner between the top loop
> and the downstroke.
I've moved some points slightly; it should be better now.
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/list
Hi all,
As some of you might have seen on the lilypond-user list, I'm working
on a Mac OS X integrated text editor/previewer for LilyPond. Several
users have asked for point-and-click support, and I'd like it too.
So, a couple clusters of questions on this topic:
(1) As I understand it, the data
Hi,
I setup a simple test to see how to lilypond takes to complete operating on a
file, on cygwin compared to on colinux.
Platform this test is ran on is on a PIII 800MHz, 359MB ram, running Windows 2k.
Cygwin is installed selecting the Lilypond 2.4.2-1 package.
coLinux (0.6.2) runs the Debian-
Hi Jürgen,
Currently, the thickness property of the flexa shape aplies to all
segments of the outline. IIUC, you are suggesting to apply the
thickness property only to the left and right outline segment of the
flexa shape, while hard-wiring the upper and lower segment wrt to the
proportions in the
Han-Wen,
Another of all these quick bug fixes! Thanks for your hard work!
It would be great if you (and others who fix bugs in CVS) could also
send a reply to the original bug report that the problem has been fixed.
I seem to recall that you sent the same request to me and others some
years ago and
Werner LEMBERG writes:
> Uh, oh, I'm neither an expert in python programming nor a regexp guru,
> sorry.
Ok. No problem.
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
[EMAIL PROTECTED] writes:
> > > * mf/feta-klef.mf (draw_gclef): Replace `simple_serif' for
> > > top of the glyph with smooth curve.
> >
> > while you're at it, can you have a look at the G clef in feta-11?
> > The upper loop has an odd bulge at the left.
>
> I don't see a problem. Please pr
> > Here some comments on parts where its formatting is not optimal.
>
> I agree with your suggestions, but most seem non-trivial. I would
> be delighted if you could fix some of them, otherwise they'll
> probably have to wait a bit.
Uh, oh, I'm neither an expert in python programming nor a rege
> > * mf/feta-klef.mf (draw_gclef): Replace `simple_serif' for
> > top of the glyph with smooth curve.
>
> while you're at it, can you have a look at the G clef in feta-11?
> The upper loop has an odd bulge at the left.
I don't see a problem. Please provide an image.
Werner
_
12 matches
Mail list logo