In that case it's better to implement an additional command
like \lilypondmusicglyph{scripts.turn} that lilypond-book
will recognize and replace with the appropriate TeX code
(hmm, what should be done for the HTML mode?).
This looks like a project beyond 2.6./Mats
Graham Percival wrote:
On 20-May-05, at 5:24 AM, Mats Bengtsson wrote:
See the comment I added in the manual for lilypond-book.
What were we saying about bug reports and feature requests in the comments of the manual? :)
Comment removed from lilypond-book.itely: ** AARGH. the titledefs and feta20.tex files will not be found now that the lilypond-profile isn't used anymore!!! /Mats
If users input the location of feta20.tex manually, could it still work? ie
\documentclass... \include{/path/to/feta20.tex}
Actually, what about doing it at compile time? When we're compiling lilypond-book.py, lilypond knows where feta20.tex is, right? So we could write that value into the compiled lilypond-book, and when lilypond-book does the .lytex -> .tex conversion, we could add the required \include, \usepackage, \input, or whatever it needs. Just like the \usepackage{graphicx}
Cheers, - Graham
-- ============================================= Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe =============================================
_______________________________________________ lilypond-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-devel
