Juergen Reuter <[EMAIL PROTECTED]> wrote:
>
> This is a known annoying problem (not only) with ancient notation, but
> harmless. Just consider it as a reminder for the developers; see the
> thread starting at:
>
> http://lists.gnu.org/archive/html/lilypond-devel/2004-09/msg00073.html
If it
Great, thanks!
Bert
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Erik Sandberg <[EMAIL PROTECTED]> wrote:
> Using debian/testing.
>
> make output with 2.4 cvs of make clean; ./autogen.sh; make:
>
> []
> FontForge used to be named PfaEdit.
>
> mv feta-braces-g.pfa ./out
> mftrace --encoding feta-braces-h.enc -I ./out/ --pfa --simplify feta-braces-h
> sh:
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
> GNOME BACKEND FOR POINT AND CLICK
>
I would like to help on this (xDVI always crashes here, I don't have
point and click working, besides with gnome backend).
> COMMUNICATION
>
> The development team should be present at the 2005 Linux Audio
> Devel
Marco Gusy writes:
> Yes it does, but there is a plan to have direct .ps output
Well, if all you need is latin1 encoding of texts and lyrics, 2.4.0
has the option full fledged direct PostScript output.
The option of using TeX constructs can be switched on by setting
\encoding "TeX".
Jan.
--
J
Alle 06:13, domenica 7 novembre 2004, J L ha scritto:
> I don't know anything about Lilypond's code, but was just wondering how
> much/whether Lilypond 2.4.x still uses TeX for typesetting of text on
> scores?
Yes it does, but there is a plan to have direct .ps output.. see "battle-plan
for 2.5 d
Bertalan Fodor writes:
> I can see that 2.4.0 is not able to correctly handle characters that
> are not in the bad old latin1 encoding - if they are written with TeX
> markup, the spacing is bad.
The patch below fixes TeX encoding. I do not expect a fix for
PostScript any time soon, probably not
