> it's not such a big problem if in texinfo encoding doesn't work
> well.
IMHO it is nice if it works, isn't it? A similar solution to the one
I've sent to bug-lilypond will probably be included in texinfo also.
Werner
___
lilypond-devel mailin
At least, it should work in the examples showing that LilyPond
can handle these characters.
/Mats
Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
./lily-2048517126.tex:138: Undefined control sequence
This is temporarily fixed now. I have to add a *lot* of macros to
make it really work -- fo
[EMAIL PROTECTED] writes:
> > ./lily-2048517126.tex:138: Undefined control sequence
>
> This is temporarily fixed now. I have to add a *lot* of macros to
> make it really work -- for texinfo mode, we have to handle T1 font
> encoding by ourselves...
it's not such a big problem if in texinfo
> ./lily-2048517126.tex:138: Undefined control sequence
This is temporarily fixed now. I have to add a *lot* of macros to
make it really work -- for texinfo mode, we have to handle T1 font
encoding by ourselves...
Werner
___
lilypond-devel
[EMAIL PROTECTED] writes:
>
> I've hacked LilyPond so that TeX output now works correctly with
> latin1 as input encoding and the EC Type 1 fonts. It is meant as a
> temporary solution until we find time to implement something better.
> This is something for a meeting :-)
Great!
However, I've n
Werner LEMBERG writes:
> I've hacked LilyPond so that TeX output now works correctly with
> latin1 as input encoding and the EC Type 1 fonts. It is meant as a
> temporary solution until we find time to implement something better.
Thanks, that's great.
> This is something for a meeting :-)
Yes,
I've hacked LilyPond so that TeX output now works correctly with
latin1 as input encoding and the EC Type 1 fonts. It is meant as a
temporary solution until we find time to implement something better.
This is something for a meeting :-)
Werner
_
