[EMAIL PROTECTED] writes:
> With current cvs:
I think you need to rerun configure.
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/
[EMAIL PROTECTED] writes:
> Log message:
> Prepare glyph shapes for mf2pt1 conversion.
Why are you doing this? I have the impression that without filldraw,
the MF code becomes (slightly) more complex. Am I missing something?
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.
With current cvs:
lilytest:~/lily/lilypond$ make
make --no-builtin-rules PACKAGE=LILYPOND package=lilypond -C buildscripts all
&& make --no-builtin-rules PACKAGE=LILYPOND package=lilypond -C python all
&& make --no-builtin-rules PACKAGE=LILYPOND package=lilypond -C scripts all
&& make --no-b
On Sunday 19 December 2004 15.56, Han-Wen Nienhuys wrote:
> LilyPond 2.5.4 is out. This release has some major brainsurgery in the
> font handling. As of now, LilyPond loads the music fonts in OpenType
> font format using FreeType. This has made a lot of things simpler,
> including font handling f
The following file
{
c''2
\repeat percent 2 { c''8 d'' }
}
compiles with a warning:
-
GNU LilyPond 2.4.2
Processing `foo.ly'
Parsing...
Interpreting music... warning: Don't know how to handle a percent
repeat of this length.
[2]
Preprocessing graphical objects...
Calculating line breaks...
