Re: Lilypond-book docs incorrect
Yes - mea culpa. I will order the sackcloth today ... You are absolutely right that using the correct docs for my Lilypond version (2.8) works, namely: mkdir outputs lilypond-book --psfonts --output=outputs/ myarticle.lytex cd outputs latex myarticle.tex dvips -o -h myarticle.psfonts -Ppdf myarticle.dvi ps2pdf myarticle.ps This is from http://www.lilypond.org/doc/v2.8/Documentation/user/lilypond/Invoking-lilypond_002dbook.html#Invoking-lilypond_002dbook The page for 2.10 is similar: http://lilypond.org/doc/v2.10/Documentation/user/lilypond/Invoking-lilypond_002dbook#Invoking-lilypond_002dbook However, I have just seen Mats comment about 2.10, which seems to suggest that for a pdf the commands should be: lilypond-book --pdf -o output=outputs/ myarticle.lytex cd outputs pdflatex myarticle.tex dvips -o -h myarticle.psfonts -Ppdf myarticle.dvi ps2pdf myarticle.ps I will try this when I am able to upgrade to 2.10. In the meantime, much to my delight, Kile is able to make all the 2.8 compile steps above a one-click option, and I want to document that somewhere now that I have it working. On a more general docs point, I do wonder if there would be merit in flagging the docs to point out more clearly mismatches between them and the version? There is currently a strip along the bottom giving the version, but I missed it entirely. Would it be possible to move this to the top of the page, put a big red border around it, and change the text to something like This info relates to an obsolete version x-x-x of Lilypond - go here to read docs for the current stable version. Then plonkers like me won't waste time trying to sort out something that has already been sorted by your good selves. -- Pob hwyl / Best wishes Kevin Donnelly www.klebran.org.uk - Gwirydd gramadeg rhydd i'r Gymraeg www.eurfa.org.uk - Geiriadur rhydd i'r Gymraeg www.rhedadur.org.uk - Rhedeg berfau Cymraeg ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Lilypond-book docs incorrect
Kevin Donnelly wrote: Yes - mea culpa. I will order the sackcloth today ... You are absolutely right that using the correct docs for my Lilypond version (2.8) works, namely: mkdir outputs lilypond-book --psfonts --output=outputs/ myarticle.lytex cd outputs latex myarticle.tex dvips -o -h myarticle.psfonts -Ppdf myarticle.dvi ps2pdf myarticle.ps This is from http://www.lilypond.org/doc/v2.8/Documentation/user/lilypond/Invoking-lilypond_002dbook.html#Invoking-lilypond_002dbook The page for 2.10 is similar: http://lilypond.org/doc/v2.10/Documentation/user/lilypond/Invoking-lilypond_002dbook#Invoking-lilypond_002dbook However, I have just seen Mats comment about 2.10, which seems to suggest that for a pdf the commands should be: lilypond-book --pdf -o output=outputs/ myarticle.lytex cd outputs pdflatex myarticle.tex dvips -o -h myarticle.psfonts -Ppdf myarticle.dvi ps2pdf myarticle.ps No! pdflatex will directly create a PDF file, so there's no need for the dvips and ps2pdf commands. This is documented in Invoking lilypond-book in the manual for version 2.10. If you check the manual for version 2.11 (which almost completely is relevant also for version 2.10 and which is significantly reworked and improved compared to the manual for 2.10, you will find that the pdflatex alternative is described as the main alternative, already in http://lilypond.org/doc/v2.11/Documentation/user/lilypond-program/An-example-of-a-musicological-document#An-example-of-a-musicological-document /Mats ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Lilypond-book docs incorrect
For the record, the recommended procedure in version 2.10 and later is lilypond-book --pdf -o out ... cd out pdflatex ... I don't remember if this works also in 2.8. /Mats Kevin Donnelly wrote: The only docs I can find on lilypond-book (http://www.lilypond.org/doc/v2.1/Documentation/user/out-www/lilypond/Integrating-text-and-music.html#Integrating-text-and-music) appear to be misleading without further information. The instructions are as follows: (1) insert lilypond markup in a .tex file (mybook.tex); (2) mkdir outputs; (3) lilypond-book --output=outputs/ mybook.tex; (4) cd outputs; (5) latex mybook; (6) dvips -Ppdf -u +lilypond mybook; (7) ps2pdf mybook.ps. (I suppose that in theory all the above steps could be combined into a switch that is passable to lilypond-book saying make me a pdf out of this tex file, please, but there may be some reason why this has not been done.) The above process gives a pdf in which the notation is missing noteheads and other things like clefs. In turn, this appears to be linked to the workflow being unable to access the Feta font at some stage(s). Item (3) therefore needs to read: lilypond-book --psfonts --output=outputs/ mybook.tex but the same issue must also occur elsewhere, probably at (7). I have been trying various permutations with various programs and googling for around 10 hours now, and I've given up. Apparently lilypond-book is the recommended way of doing this (since the lilypond --tex approach is no longer properly supported), but it plainly doesn't work as advertised. Several of the pages I turned up via Google recount people's problems with getting the Feta font seen by LaTeX, but there seems to be no good (ie easily-applicable) solution to that issue either (the current fonts have no .fd file, for instance, so they would need to be compiled from source, which is not something everyone can do). What I'm doing now is to generate a pdf from the .ly file produced by Rosegarden (which is a terrific visual front-end for Lilypond) for each of the notation snippets I wanted to reference, take a snapshot of it at 200%, crop and reduce it in GIMP, and then insert it as a picture in KWord. The snippets come out slightly fuzzy, but the process is considerably simpler and less time-consuming than the lilypond-book option, and produces a useable result. It's very sad that an excellent project like Lilypond, dedicated to producing high-quality notation engraving, doesn't seem to offer a reliable and documented way of working with LaTeX, dedicated to producing high-quality typesetting, even though they are both based on the same TeX engine, and even though it would seem that they are ideal companions. Rosegarden can take its notation view and convert it via Lilypond into a pdf at the click of a button, and it's not clear why converting a tex file into a pdf should be so much harder. For the record, I am using: openSUSE 10.2 lilypond 2.8.7-15 te_latex 3.0-58 Kevin Donnelly ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond -- = Mats Bengtsson Signal Processing School of Electrical Engineering Royal Institute of Technology (KTH) 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 = ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Lilypond-book docs incorrect
2008/3/10, Kevin Donnelly [EMAIL PROTECTED]: The only docs I can find on lilypond-book (http://www.lilypond.org/doc/v2.1/Documentation/user/out-www/lilypond/Integrating-text-and-music.html#Integrating-text-and-music) These instructions are for Lilypond 2.1 (date unknown), your version is 2.8 (oct 2006) latest stable is 2.10 (2.10.33 is from Sep '07), latest development issue is three days ago. I think you'd have saved much time first going to lilypond.org and following the Documentation--lilypond2.10-User manual. Once there, search for the string -book, follow the link and you'll find that the --psfonts option is there. If you can, uninstall your current lilypond and re-install it from latest stable or development installer binaries. Bookmark the current docs and don't rely so much in Google for such a rapid changing documentation. BTW lilypond-book works perfectly in most cases, if not, ask here. -- Francisco Vila. Badajoz (Spain) http://www.paconet.org ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Lilypond-book docs incorrect
You seem to be using the documentation for version 2.1. Go to the link in your message and replace v2.1 in the URL with v2.8 (or v2.10 for the latest version). The newer version of that page does explain about the psfonts option, and contains a link to section 13.6 Invoking lilypond-book which tells you how to feed the psfonts file to dvips. Message: 11 Date: Mon, 10 Mar 2008 14:44:08 + (UTC) From: Kevin Donnelly [EMAIL PROTECTED] Subject: Lilypond-book docs incorrect To: bug-lilypond@gnu.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii The only docs I can find on lilypond-book (http://www.lilypond.org/doc/v2.1/Documentation/user/out-www/lilypond/Integrating-text-and-music.html#Integrating-text-and-music) appear to be misleading without further information. The instructions are as follows: (1) insert lilypond markup in a .tex file (mybook.tex); (2) mkdir outputs; (3) lilypond-book --output=outputs/ mybook.tex; (4) cd outputs; (5) latex mybook; (6) dvips -Ppdf -u +lilypond mybook; (7) ps2pdf mybook.ps. (I suppose that in theory all the above steps could be combined into a switch that is passable to lilypond-book saying make me a pdf out of this tex file, please, but there may be some reason why this has not been done.) The above process gives a pdf in which the notation is missing noteheads and other things like clefs. In turn, this appears to be linked to the workflow being unable to access the Feta font at some stage(s). Item (3) therefore needs to read: lilypond-book --psfonts --output=outputs/ mybook.tex but the same issue must also occur elsewhere, probably at (7). I have been trying various permutations with various programs and googling for around 10 hours now, and I've given up. Apparently lilypond-book is the recommended way of doing this (since the lilypond --tex approach is no longer properly supported), but it plainly doesn't work as advertised. Several of the pages I turned up via Google recount people's problems with getting the Feta font seen by LaTeX, but there seems to be no good (ie easily-applicable) solution to that issue either (the current fonts have no .fd file, for instance, so they would need to be compiled from source, which is not something everyone can do). What I'm doing now is to generate a pdf from the .ly file produced by Rosegarden (which is a terrific visual front-end for Lilypond) for each of the notation snippets I wanted to reference, take a snapshot of it at 200%, crop and reduce it in GIMP, and then insert it as a picture in KWord. The snippets come out slightly fuzzy, but the process is considerably simpler and less time-consuming than the lilypond-book option, and produces a useable result. It's very sad that an excellent project like Lilypond, dedicated to producing high-quality notation engraving, doesn't seem to offer a reliable and documented way of working with LaTeX, dedicated to producing high-quality typesetting, even though they are both based on the same TeX engine, and even though it would seem that they are ideal companions. Rosegarden can take its notation view and convert it via Lilypond into a pdf at the click of a button, and it's not clear why converting a tex file into a pdf should be so much harder. For the record, I am using: openSUSE 10.2 lilypond 2.8.7-15 te_latex 3.0-58 Kevin Donnelly -- ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond End of bug-lilypond Digest, Vol 64, Issue 10 -- GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen! Jetzt dabei sein: http://www.shortview.de/[EMAIL PROTECTED] ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
