> I appreciate the patch, but lilypond.py will change for lily 3.0.
I've noticed that already (without testing).
> Our plan is that lilypond.py will use direct PS. Special
> functionality, like LaTeX packages and non-standard (non-latin)
> font-encoding should be dealt with by writing your own .tex wrapper
> file around lilypond-bin's tex output, or using lilypond-book.
For me, this has to wait until autumn. As mentioned earlier, the
next few weeks I'll use the 2.2. series exclusively (except a problem
appears which can't be solved).
Werner
_______________________________________________
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
