Re: texinfo manual?
"Hwaen Ch'uqi" writes: > Gretings, > > Have you found a remedy for the problem of broken images in LilyPond's > texinfo manuals? If not, I believe I have found the answer, though at > a slight cost of self-guilt. The images are broken because, as the > manuals are now in a different directory, the file paths of the images > given in the source code no longer work. The easiest solution is to > return the texinfo files to their original directory (which in my case > was /usr/lilypond/usr/share/info) and to modify the LilyPond entries > in your /usr/share/info/dir file to reflect the manuals' new location. > So, for example, if the entry for the notation manual looks something > like this, > > * LilyPond Notation Reference: (lilypond-notation). > > then you should edit it to look something like this: > > * LilyPond Notation Reference: > (/usr/lilypond/usr/share/info/lilypond-notation). > > (Of course, this may vary slightly depending upon where you installed > LilyPond.) Finally, make ABSOLUTELY CERTAIN that, in the directory > where you have returned the info files, there is still a lilypond > link. In my dired buffer, the full line reads like this: > > lrwxrwxrwx 1 hwaen 1002 35 Mar 17 13:04 lilypond -> > ../doc/lilypond/html/Documentation/ > > Without this symbolic link, which is assumed to exist by the given > path of each png file in the source code of the manuals, you will > still see no images. > > So, in sum, the original answer to your question should have been a > lot smoother, and that was merely to put entries in your > /usr/share/info/dir file that acknowledged the existence of the > LilyPond texinfo files and indicated where the texinfo reader could > find them. I am sorry to have initially misdirected you, and I should > have waited until my own emacs was running again before advising you. > If your have further questions, you may write to me off-list, as I > believe the necessary information for Lily users who use texinfo > manuals on emacs has now been covered. > > Hwaen Ch'uqi > Thanks for getting back to me about this! I tried to follow your instructions here, but became confused due to my inexperience mucking around outside of my ~/ directory. However, since you also suggested what would have been a more straightforward solution to my original query, I uninstalled Lilypond and reinstalled again with the --documentation switch. Then I corrected the links in my /usr/share/info/dir document as you suggested, and now everything works as it should---images and all. Thank you again, Steven ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: texinfo manual?
Gretings, Have you found a remedy for the problem of broken images in LilyPond's texinfo manuals? If not, I believe I have found the answer, though at a slight cost of self-guilt. The images are broken because, as the manuals are now in a different directory, the file paths of the images given in the source code no longer work. The easiest solution is to return the texinfo files to their original directory (which in my case was /usr/lilypond/usr/share/info) and to modify the LilyPond entries in your /usr/share/info/dir file to reflect the manuals' new location. So, for example, if the entry for the notation manual looks something like this, * LilyPond Notation Reference: (lilypond-notation). then you should edit it to look something like this: * LilyPond Notation Reference: (/usr/lilypond/usr/share/info/lilypond-notation). (Of course, this may vary slightly depending upon where you installed LilyPond.) Finally, make ABSOLUTELY CERTAIN that, in the directory where you have returned the info files, there is still a lilypond link. In my dired buffer, the full line reads like this: lrwxrwxrwx 1 hwaen 1002 35 Mar 17 13:04 lilypond -> ../doc/lilypond/html/Documentation/ Without this symbolic link, which is assumed to exist by the given path of each png file in the source code of the manuals, you will still see no images. So, in sum, the original answer to your question should have been a lot smoother, and that was merely to put entries in your /usr/share/info/dir file that acknowledged the existence of the LilyPond texinfo files and indicated where the texinfo reader could find them. I am sorry to have initially misdirected you, and I should have waited until my own emacs was running again before advising you. If your have further questions, you may write to me off-list, as I believe the necessary information for Lily users who use texinfo manuals on emacs has now been covered. Hwaen Ch'uqi On 8/19/14, Steven Arntson wrote: > > "Hwaen Ch'uqi" writes: > >> Greetings, >> >> I have never used `C-u C-h i', and my emacs is currently down, so I >> canot exactly replicate your situation. However, one thing I have >> consistently had to do with these installations is to manualy update >> the dir file in the /usr/share/info directory; this is why some files >> may not appear to be present upon first glance. Again, this will >> likely have to be done as root. Before making any changes to the file, >> study carefully its contents; you will want to emulate the format in >> your own additions. Basically, each entry consists of four parts. The >> first is the asterisk (*), which tells the info reader that a new >> entry has begun. The second is the title which you would like to see >> given in the main menu. I don't remember offhand, but it may be >> followed immediately by a colon (:); if so, you MUST include this. The >> third is the actual file names without the .info extension; make sure >> that it is placed in parentheses, matches exactly the case of the file >> name (since case sensitivity rules in linux), and is closed with a >> period (>) AFTER the parentheses. Finally, fourth is the short >> description of the file's contents. I have found that the last part is >> optional. Your current dir file will most likely not have a LilyPond >> section heading. You can easily instantiate one, preceding it with two >> newlines and following it with one. I recall that in ubuntu's >> installation, there was the possibility of quickly entering >> subsections of the LilyPond manuals. I don't know how to do this, but >> I believe that entries in the dir file should reveal this. >> >> One final note: I have found that, when adding or updating a program >> via the automated process, and if it comes with an info file, ubuntu >> will rewrite the dir file, and your contributions wil be missing. Not >> to panic! A backup file, dir~, will be made, and you should find your >> changes there. Copy them and insert them into the new dir file. It is >> a small inconvenience, but it is worth the ability to use the latest >> versions of LilyPond! >> >> I hope this answer was somewhat useful. >> >> Hwaen Ch'uqi >> > > Thank you for the description---that all worked perfectly, and I can get > to everything with C-h i! > > My only issue now is that in the manuals, none of the images display. In > every case where there would be a music example, it says, "[broken image]." > > Thanks again, this is a much better situation already than what I had > before! > > -steven > > > ___ > lilypond-user mailing list > lilypond-user@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: texinfo manual?
"Hwaen Ch'uqi" writes: > Greetings, > > I have never used `C-u C-h i', and my emacs is currently down, so I > canot exactly replicate your situation. However, one thing I have > consistently had to do with these installations is to manualy update > the dir file in the /usr/share/info directory; this is why some files > may not appear to be present upon first glance. Again, this will > likely have to be done as root. Before making any changes to the file, > study carefully its contents; you will want to emulate the format in > your own additions. Basically, each entry consists of four parts. The > first is the asterisk (*), which tells the info reader that a new > entry has begun. The second is the title which you would like to see > given in the main menu. I don't remember offhand, but it may be > followed immediately by a colon (:); if so, you MUST include this. The > third is the actual file names without the .info extension; make sure > that it is placed in parentheses, matches exactly the case of the file > name (since case sensitivity rules in linux), and is closed with a > period (>) AFTER the parentheses. Finally, fourth is the short > description of the file's contents. I have found that the last part is > optional. Your current dir file will most likely not have a LilyPond > section heading. You can easily instantiate one, preceding it with two > newlines and following it with one. I recall that in ubuntu's > installation, there was the possibility of quickly entering > subsections of the LilyPond manuals. I don't know how to do this, but > I believe that entries in the dir file should reveal this. > > One final note: I have found that, when adding or updating a program > via the automated process, and if it comes with an info file, ubuntu > will rewrite the dir file, and your contributions wil be missing. Not > to panic! A backup file, dir~, will be made, and you should find your > changes there. Copy them and insert them into the new dir file. It is > a small inconvenience, but it is worth the ability to use the latest > versions of LilyPond! > > I hope this answer was somewhat useful. > > Hwaen Ch'uqi > Thank you for the description---that all worked perfectly, and I can get to everything with C-h i! My only issue now is that in the manuals, none of the images display. In every case where there would be a music example, it says, "[broken image]." Thanks again, this is a much better situation already than what I had before! -steven ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: texinfo manual?
Greetings, I have never used `C-u C-h i', and my emacs is currently down, so I canot exactly replicate your situation. However, one thing I have consistently had to do with these installations is to manualy update the dir file in the /usr/share/info directory; this is why some files may not appear to be present upon first glance. Again, this will likely have to be done as root. Before making any changes to the file, study carefully its contents; you will want to emulate the format in your own additions. Basically, each entry consists of four parts. The first is the asterisk (*), which tells the info reader that a new entry has begun. The second is the title which you would like to see given in the main menu. I don't remember offhand, but it may be followed immediately by a colon (:); if so, you MUST include this. The third is the actual file names without the .info extension; make sure that it is placed in parentheses, matches exactly the case of the file name (since case sensitivity rules in linux), and is closed with a period (>) AFTER the parentheses. Finally, fourth is the short description of the file's contents. I have found that the last part is optional. Your current dir file will most likely not have a LilyPond section heading. You can easily instantiate one, preceding it with two newlines and following it with one. I recall that in ubuntu's installation, there was the possibility of quickly entering subsections of the LilyPond manuals. I don't know how to do this, but I believe that entries in the dir file should reveal this. One final note: I have found that, when adding or updating a program via the automated process, and if it comes with an info file, ubuntu will rewrite the dir file, and your contributions wil be missing. Not to panic! A backup file, dir~, will be made, and you should find your changes there. Copy them and insert them into the new dir file. It is a small inconvenience, but it is worth the ability to use the latest versions of LilyPond! I hope this answer was somewhat useful. Hwaen Ch'uqi On 8/18/14, Steven Arntson wrote: > "Hwaen Ch'uqi" writes: > >> Greetings, >> >> Hmmm. Dense? I hardly doubt it! Perhaps you might try this: Reinstall >> lilypond with the .sh script but also call for documentation, >> something like this: >> >> sudo sh LILYPONDFILENAME.sh --prefix=PATH --documentation >> >> From my experience, this will take substantially longer to download, >> but you wil then have the complete documentation locally - at least in >> html format. But it may be that this direction also grabs the texinfo >> files and places them in the aforementioned lilypond/usr/share/info >> directory? Having always downloaded and installed lilypond this way, I >> have never noticed whether the --documentation flag was neded to >> obtain the .info files. I do hope this works. >> >> Hwaen Ch'uqi >> >> >> >> On 8/18/14, Steven Arntson wrote: >>> "Hwaen Ch'uqi" writes: >>> Greetings Steven, The manuals are in Texinfo format, and the good news is that they are merely hidden. Going off the top of my head, I believe the files are located in the folder lilypond/usr/share/info. There, you should find just over 30 files, most with a .info extension. Move them to your folder called /usr/share/info. N.B. -- You may need to be root to do this. Then you should be able to access the files with `c-h i'. I hope this helps. Hwaen Ch'uqi > One thing I'm missing now is the manual in texinfo format (I think). I > use Emacs to enter my lilypond docs, and I used to have a bunch of > manuals that I could open with C-h i. I think they were in texinfo > format. Now they're gone... > > Thank you! > steven arntson >>> >>> My lilypond/usr/share contains: >>> >>> emacs >>> fonts >>> ghostscript >>> glib-2.0 >>> guile >>> lilypond >>> locale >>> >>> -steven >>> > > That worked, and I got the info files--thank you! > > Now I'm not sure how to get emacs to recognize them. I copied the files > to /usr/share/info/lilypond, and successfully viewed a couple pages with > C-u C-h i, but the whole thing isn't showing up by itself when I call > C-h i, even after restarting emacs. > > Perhaps I should pursue this in help.emacs, but thought I'd ask here > first, since I started the thread here. > > Thank you again for your help! > > > ___ > lilypond-user mailing list > lilypond-user@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: texinfo manual?
"Hwaen Ch'uqi" writes: > Greetings, > > Hmmm. Dense? I hardly doubt it! Perhaps you might try this: Reinstall > lilypond with the .sh script but also call for documentation, > something like this: > > sudo sh LILYPONDFILENAME.sh --prefix=PATH --documentation > > From my experience, this will take substantially longer to download, > but you wil then have the complete documentation locally - at least in > html format. But it may be that this direction also grabs the texinfo > files and places them in the aforementioned lilypond/usr/share/info > directory? Having always downloaded and installed lilypond this way, I > have never noticed whether the --documentation flag was neded to > obtain the .info files. I do hope this works. > > Hwaen Ch'uqi > > > > On 8/18/14, Steven Arntson wrote: >> "Hwaen Ch'uqi" writes: >> >>> Greetings Steven, >>> >>> The manuals are in Texinfo format, and the good news is that they are >>> merely hidden. Going off the top of my head, I believe the files are >>> located in the folder lilypond/usr/share/info. There, you should find >>> just over 30 files, most with a .info extension. Move them to your >>> folder called /usr/share/info. N.B. -- You may need to be root to do >>> this. Then you should be able to access the files with `c-h i'. I hope >>> this helps. >>> >>> Hwaen Ch'uqi >>> One thing I'm missing now is the manual in texinfo format (I think). I use Emacs to enter my lilypond docs, and I used to have a bunch of manuals that I could open with C-h i. I think they were in texinfo format. Now they're gone... Thank you! steven arntson >> >> My lilypond/usr/share contains: >> >> emacs >> fonts >> ghostscript >> glib-2.0 >> guile >> lilypond >> locale >> >> -steven >> That worked, and I got the info files--thank you! Now I'm not sure how to get emacs to recognize them. I copied the files to /usr/share/info/lilypond, and successfully viewed a couple pages with C-u C-h i, but the whole thing isn't showing up by itself when I call C-h i, even after restarting emacs. Perhaps I should pursue this in help.emacs, but thought I'd ask here first, since I started the thread here. Thank you again for your help! ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: texinfo manual?
"Hwaen Ch'uqi" writes: > Greetings Steven, > > The manuals are in Texinfo format, and the good news is that they are > merely hidden. Going off the top of my head, I believe the files are > located in the folder lilypond/usr/share/info. There, you should find > just over 30 files, most with a .info extension. Move them to your > folder called /usr/share/info. N.B. -- You may need to be root to do > this. Then you should be able to access the files with `c-h i'. I hope > this helps. > > Hwaen Ch'uqi > >> One thing I'm missing now is the manual in texinfo format (I think). I >> use Emacs to enter my lilypond docs, and I used to have a bunch of >> manuals that I could open with C-h i. I think they were in texinfo >> format. Now they're gone... >> >> Thank you! >> steven arntson My lilypond/usr/share contains: emacs fonts ghostscript glib-2.0 guile lilypond locale The lilypond file there contains /current, which contains: compiler ftdetect ftplugin indent syntax I've searched all around ... is it possible I downloaded 2.18.2 without these files? Sorry if I'm being dense! I am often more dense than I wish. -steven ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: texinfo manual?
Greetings, Hmmm. Dense? I hardly doubt it! Perhaps you might try this: Reinstall lilypond with the .sh script but also call for documentation, something like this: sudo sh LILYPONDFILENAME.sh --prefix=PATH --documentation >From my experience, this will take substantially longer to download, but you wil then have the complete documentation locally - at least in html format. But it may be that this direction also grabs the texinfo files and places them in the aforementioned lilypond/usr/share/info directory? Having always downloaded and installed lilypond this way, I have never noticed whether the --documentation flag was neded to obtain the .info files. I do hope this works. Hwaen Ch'uqi On 8/18/14, Steven Arntson wrote: > "Hwaen Ch'uqi" writes: > >> Greetings Steven, >> >> The manuals are in Texinfo format, and the good news is that they are >> merely hidden. Going off the top of my head, I believe the files are >> located in the folder lilypond/usr/share/info. There, you should find >> just over 30 files, most with a .info extension. Move them to your >> folder called /usr/share/info. N.B. -- You may need to be root to do >> this. Then you should be able to access the files with `c-h i'. I hope >> this helps. >> >> Hwaen Ch'uqi >> >>> One thing I'm missing now is the manual in texinfo format (I think). I >>> use Emacs to enter my lilypond docs, and I used to have a bunch of >>> manuals that I could open with C-h i. I think they were in texinfo >>> format. Now they're gone... >>> >>> Thank you! >>> steven arntson > > My lilypond/usr/share contains: > > emacs > fonts > ghostscript > glib-2.0 > guile > lilypond > locale > > The lilypond file there contains /current, which contains: > > compiler > ftdetect > ftplugin > indent > syntax > > I've searched all around ... is it possible I downloaded 2.18.2 without > these files? > > Sorry if I'm being dense! I am often more dense than I wish. > > -steven > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: texinfo manual?
Greetings Steven, The manuals are in Texinfo format, and the good news is that they are merely hidden. Going off the top of my head, I believe the files are located in the folder lilypond/usr/share/info. There, you should find just over 30 files, most with a .info extension. Move them to your folder called /usr/share/info. N.B. -- You may need to be root to do this. Then you should be able to access the files with `c-h i'. I hope this helps. Hwaen Ch'uqi On 8/17/14, Steven Arntson wrote: > I've installed the newest stable version of Lilypond on my system, > updating from the moldy version in the Ubuntu repo. It works great! > > One thing I'm missing now is the manual in texinfo format (I think). I > use Emacs to enter my lilypond docs, and I used to have a bunch of > manuals that I could open with C-h i. I think they were in texinfo > format. Now they're gone, and I'm enough of a beginner all > around that I'm not sure where they came from in the first place. Is > there a spot online somewhere where one can get them all at once, or are > they hidden somewhere in my new install? > > Thank you! > steven arntson > > > ___ > lilypond-user mailing list > lilypond-user@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Texinfo manual.
On Wed, Jun 29, 2011 at 06:18:04AM +0200, Werner LEMBERG wrote: > > > But this path wasn't valid. The index.html file was actually > > installed to > > > > file:///usr/local/lilypond/usr/share/doc/lilypond/html/offline-root/index.html > > Ouch. Why not the canonical location > > file:///usr/local/share/doc/lilypond/... ? > > This looks completely broken. LilyPond installs everything into @prefix@/lilypond/. We add symlinks to @prefix@/bin/lilypond and the like, so most people don't notice. My best guess is that this makes it easier to deal with the osx app format and/or mingw progra~1 ? but that's a complete guess. In keeping with that, I suppose that we could make the --doc add such a symlink. Anybody interested in poking at the installation scripts is of course welcome to do so, but it won't be pretty. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Texinfo manual.
> But this path wasn't valid. The index.html file was actually > installed to > > file:///usr/local/lilypond/usr/share/doc/lilypond/html/offline-root/index.html Ouch. Why not the canonical location file:///usr/local/share/doc/lilypond/... ? This looks completely broken. Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Texinfo manual.
Il giorno mer, 29/06/2011 alle 07.50 +1000, Nick Payne ha scritto: > Also, even if the manuals are installed locally, using the search > facility still goes to the web and uses Google to search the online > documentation. That's not avoidable, since the search engine is Google :-) The nicest solution would be the documentation builded by Reinhold: http://www.kainhofer.com/~lilypond/Documentation/notation/index.html#top There's an open issue about it: http://code.google.com/p/lilypond/issues/detail?id=1270 Another possible solution is the index mapping of tools such as Sphinx. For example, the Python documentation: http://docs.python.org/ Here you can find an explanation of how it works: http://groups.google.com/group/sphinx-dev/browse_thread/thread/956ea67482471fdd/6814090ac610b7ac?lnk=gst&q=search+index#6814090ac610b7ac Cheers, Federico ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Texinfo manual.
On 29/06/11 04:42, Graham Percival wrote: On Tue, Jun 28, 2011 at 06:34:45PM +0200, Michel Villeneuve wrote: Did you try install lilypond with the --doc option ? sh lilypond-2.14.1-1.linux-x86.sh --doc woah, I had no idea that existed! James: please add a """ Help In the shell, type: sh lilypond-51234.sh --help """ to the Unix download page on the website. Push directly when you're done, unless you're feeling really uncertain for some reason. I just tried this. I already had the install file and doc tarball for 2.14.1 downloaded to the same folder, and using the --doc option used the already-downloaded doc tarball to install the documentation. However, the message the installer puts out at the end of the install gives the wrong location for the documentation. The installer prints out: "Full documentation can be found at file:///usr/local/lilypond/usr/share/doc/lilypond/html/index.html file:///usr/local/lilypond/usr/share/info/dir" But this path wasn't valid. The index.html file was actually installed to file:///usr/local/lilypond/usr/share/doc/lilypond/html/offline-root/index.html and the actual (English) documentation is at file:///usr/local/lilypond/usr/share/doc/lilypond/html/offline-root/Documentation/web/manuals.html Also, even if the manuals are installed locally, using the search facility still goes to the web and uses Google to search the online documentation. Nick ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Texinfo manual.
Hello, From: Graham Percival [gra...@percival-music.ca] Sent: 28 June 2011 19:42 To: Michel Villeneuve; James Lowe Cc: Hwaen Ch'uqi; lilypond-user@gnu.org Subject: Re: Texinfo manual. On Tue, Jun 28, 2011 at 06:34:45PM +0200, Michel Villeneuve wrote: > Did you try install lilypond with the --doc option ? > > sh lilypond-2.14.1-1.linux-x86.sh --doc woah, I had no idea that existed! James: please add a """ Help In the shell, type: sh lilypond-51234.sh --help """ to the Unix download page on the website. Push directly when you're done, unless you're feeling really uncertain for some reason. Added as 12503a0c383617cd11fa0bba2836af6c0518ecf7 James ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Texinfo manual.
On Tue, Jun 28, 2011 at 06:34:45PM +0200, Michel Villeneuve wrote: > Did you try install lilypond with the --doc option ? > > sh lilypond-2.14.1-1.linux-x86.sh --doc woah, I had no idea that existed! James: please add a """ Help In the shell, type: sh lilypond-51234.sh --help """ to the Unix download page on the website. Push directly when you're done, unless you're feeling really uncertain for some reason. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Texinfo manual.
2011/6/28 Hwaen Ch'uqi : > Greetings All, > I have just downloaded and installed the x86 distribution of > LilyPond-2.14.1. I may be missing something fantastically obvious, but > I am unable to locate a manual which I can read through Emacs' texinfo > facility. Any help is appreciated! > Hwaen Ch'uqi Did you try install lilypond with the --doc option ? sh lilypond-2.14.1-1.linux-x86.sh --doc Then the documentation is downloaded and uncompressed and available here : file:///home/user/lilypond/usr/share/doc/lilypond/html/index.html file:///home/user/lilypond/usr/share/info/dir Maybe the second one is the appropriate format that you're looking for.. Hope it helps. -- Michel Villeneuve ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Texinfo manual.
"Hwaen Ch'uqi" writes: > Greetings All, > I have just downloaded and installed the x86 distribution of > LilyPond-2.14.1. I may be missing something fantastically obvious, but > I am unable to locate a manual which I can read through Emacs' texinfo > facility. Any help is appreciated! Emacs has no "texinfo facility" but rather an _info_ reader. When installing from source, you need to separately call "make info" and "sudo make install-info" in order to get the info manuals in place (including graphics that current versions of Emacs can display). I have no idea whether the documentation comes in a separate distribution if you install precompiled binaries. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
