![]() Use Lilypond-book to produce the document with the snippets sans text and then use XeLaTeX to add the text you want on top of the lilypond snippets. But once you get the hang of the syntax it ain't so bad and it makes compiling and introducing snippets much easier since it does not rely on any outside software or multiple compiles.Ī third crazier idea. And it doesn't have all the nice automatic spacing algorithms. It will have around 1,200 snippets of music so instead of fiddling with lilypond-book or even just lilypond and inserting all of those outside pdfs I'm doing them in MusixTeX. That's what I'm doing on my latest project. I know snippets are trickier to deal with than full pages but it should work pretty well. I do this for most of my scores where I use Lilypond to produce the full pages and then LuaTeX to handle the front and back covers and all the other text. From what I understand this is what lilypond-book does anyway. The first is to avoid lilypond-book altogether and just compile the lilypond code separately as snippets and then insert the pdfs into your XeLaTeX document. So, I don't have a direct answer but two alternative approaches occur to me. Interesting, I didn't know that lilypond-book would not respect your font declarations like that. at least you get consistent fonts though! If your output is for the web, you can add a CSS property to it and will look better than exporting the shadow in the GIF directly (will be better quality). Since the lilypond part of the document is getting its fonts from pango (not fontspec/xelatex), any OpenType features that show up in the TeX document won't show up in the Lilypond output. Simply enlarge your document, add a background color as the background color where the GIF will be placed, then add your shadow to your GIF. \override LyricText #'font-family = #'romanĪnd then run: lilypond-book -latex-program=xelatex test.lytex
0 Comments
Leave a Reply. |