> 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
[EMAIL PROTECTED] writes:
>
> Here my results typesetting a Japanese folk song (Sakura sakura) and a
> Chinese children song (Xiao haizi guai guai) with version 2.2.4.
>
> The current `lilypond' script must be extended to pass more
> information:
>
> . Two new \header fields `atbegindocument'
> > For my tests, I've used Dominique Unruh's `unicode' package.
>
> Unfortunately, the latest LaTeX release also provides a `utf8.def'
> file which you must rename to `utf-8.def'.
The original message sits in the moderator's queue since it is too
big.
Werner
> For my tests, I've used Dominique Unruh's `unicode' package.
Unfortunately, the latest LaTeX release also provides a `utf8.def'
file which you must rename to `utf-8.def'.
Werner
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gn
