On Wednesday, 22 April 1998, Jan Arne Fagertun writes:
> Onsdag den 22. april 1998 skrev Janne:
>
> > A lot of code is not written to be efficient, so quite some
> > speed improvements can be made (the junking of libg++ Rational
> > was quite an improvement accidentally...)
>
> Well - I think you'll have to struggle very hard to reduce the
> lilypond time consumption to close to that of LaTeX, at least
Okay, i didn't want to suggest matching TeX's execution time.
Sure, typesetting a piece of music is a lot harder than stacking
line-boxes on a page and calculating page breaks. Still, Lily
can be quite a bit quicker.
> My last successfull installation of lilypond was 0.1.47, so I
> haven't seen any los-toros. But I struggled a lot with another
> piece of music, "standchen.ly", to make the title look good:
We switched back to our own make-system, so if its just that
you had problems building...
> 1) You have to tell ly2dvi which language you want LaTeX to use
> - i.e. 'ly2dvi --lang=german standchen'. If not, it will use
> english.
Aha, but surely \'e should work in english (american) too?
>
> 2) Lilypond strips off one '\', so "\'e" looks like "'e" after
> lilyponding it. Add another '\' to "\\'e", and it should be OK.
Ah, yes, but quoting from los-toros:
g2->^"Un peu plus lent et \\'el\\'egant" ~ |
something goes wrong using ly2dvi..
Btw, i don't like the parentheses around 'lily was here', they
make it look as an excuse rather than a statement, imo.
Jan.
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | LilyPond - The GNU music typesetter
http://www.digicash.com/~jan | http://www.cs.ruu.nl/people/hanwen/lilypond
