[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[PATCH] ancient breathing signs; feta-schrift additions

From: Han-Wen Nienhuys
Subject: [PATCH] ancient breathing signs; feta-schrift additions
Date: Sat, 22 Mar 2003 01:33:30 +0100

address@hidden writes:
> Hi!
> Here's another patch (next time I will try to directly access CVS).
> Unfortunately, the docu does not build anymore:
> /usr/bin/python ../../scripts/ <...snip...> lilypond.tely
> lilypond-book (GNU LilyPond) 1.7.15
> <...snip...>
> Reading `/home/reuter/project/lilypond-1.7/mf/out/'
> Traceback (most recent call last):
>   File "../../scripts/", line 1543, in ?
>     do_file (input_filename)
>   File "../../scripts/", line 1403, in do_file
>     chunks = chop_chunks (chunks, 'lilypond-block', make_lilypond_block, 1)
>   File "../../scripts/", line 955, in chop_chunks
>     m = get_re (re_name).search (str)
> RuntimeError: maximum recursion limit exceeded
> This is probably the same problem that we already had with the parmesan
> font: the font character list file just got too big due to the increasing
> number of characters in the font.  Any idea what to do?  Maybe splitting
> feta once more into pieces?

Thanks for the patch, I've added it to CVS.

I've bought us a little time by using \char #NUMBER in stead of
\musicglyph #NAME. Another solution would be to use some sort of
inline scheme code to generate the table directly from the AFM file.

[..a little hacking..]

However, it seems that we have some kind of hard limit on how large a
lilypond fragment can be. This is a little disturbing -- I've changed
lilypond-book so that @lilypondfile{} does not use an intermediate

        @end lilypond

This means that lilypond-book can handle arbitrarily large files when
used through @lilypondfile.


Han-Wen Nienhuys   |   address@hidden   | 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]