Our music book's pieces are almost completed, and I've written most of
them in LilyPond (updating it from CVS frequently).
There's a lot of non-trivial notation and many places where I had to
resort to tricks to get clean output.
Would it be useful for you developers if I share the .ly source of
Erik Sandberg <[EMAIL PROTECTED]> writes:
> Pedro, I know you're using something like debian/testing also.. do you have a
> clue of what could be wrong? Also, are you planning to make a gnome-enabled
> debian package of lily 2.5 soon? (in that case I could wait for that before
> testing gnome ou
On Sat, 11 Dec 2004, Han-Wen Nienhuys wrote:
> - Font_metric *f = 0;
> - if ((name.left_string (4) == "feta")
> + Font_metric *f = find_otf (name);
> +
> +
> + if (!f &&
> + (name.left_string (4) == "feta")
>|| (name.left_string (8) == "parmesan")
>|| (name.left_string
Hi,
I have some preliminary boilerplate for generating an OTF (see
mf/merge.pe), and reading OTFs from LilyPond (btw: does FT complain if
I load the .t42 file?). I've decided to use FT for the feta font for
now; I only want to deal with 1 complication at a time.
How do I translate from feta20.ot
