In article <[EMAIL PROTECTED]>, Mats Bengtsson <[EMAIL PROTECTED]> wrote:
> Walter Hofmeister wrote: > > > > Michael, > > Check here: http://www.dimi.uniud.it/vitacolo/freesoftware.html > > > > Thanks to Nicola Vitacolonna for this bit of software. > > > > Scroll down the page about half-way to the Desktop Publishing section. At > > the bottom of the section you will see a link with instructions to get the > > Lilypond engine working with TexShop. Note that point and click does NOT > > work with TexShop (it is not compatible). Make sure that TexShop is set to > > save files in UTF-8 Unicode format or Lilypond will choke. > > > Won't LaTeX choke on the LaTeX parts of the documents then? > Unless you have a UTF-8 capable LaTeX, the best solution I see is > to write the LilyPond code in separate files (saved in UTF-8) that then > are included into the LaTeX document (saved in ISO 8859-1 or whatever) > using \lilypondfile{...}. I would recommend using \usepackage[utf8x]{inputenc} and saving the LaTeX file as UTF-8. Then, you can input Unicode directly. An alternative would be the use of XeTeX, but I do not know if Lilypond can work with XeTeX. > Nicola, I took a quick look into > http://www.dimi.uniud.it/vitacolo/download/software/latex/Lilypond-LaTeX.engin > e.txt > and noticed that you use latex + dvips + ps2pdf to process the file. I > hope you are > aware of the possibility to instead use pdflatex: > lilypond-book -o out --pdf myfile.lytex > cd out > pdflatex myfile.tex > > Since TexShop seems to use pdflatex by default, this seems like a > preferable solution. Yes, of course. Actually, I would like to re-write the engine, because I have realized that putting lilypond-book output into out and cd'ing there is not, in general, a good idea: (pdf)latex may not be able to find external files (e.g., local style files, .bib files, pictures included with \includegraphics, other .tex files, etc...). Initially, I thought that the engine could be changed so as to figure out what needs to be copied into out, but that is not trivial, given the abundance of ways external files may be accessed. So, the only feasible solution, in my opinion, is to have lilypond-book output files in the same directory as the source file (and make some cleaning at the end of the process). This is complicated by the fact that lilypond-book complains if there are name clashes. Is there any way to tell lilypond-book the name of its generated .tex file(s)? > I have added a few lines of information about this LilyPond support in > TexShop > in the section on Editor support in the manual. Thank you. I would also like to mention, if it is not known already, that Smultron has syntax colouring definitions for Lilypond. TeXShop can be configured to use Smultron as an external text editor. Regards Nicola _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
