Re: musescore
Mike Blackstock schreef op do 09-12-2010 om 17:06 [-0800]: Hi Mike, I have around 2800 FB friends, nearly all of them musicians, and I plan to do some Lilypond advocacy - hence my friend request. I'll need some 'backup' debaters/advisors etc. and so if anybody would like to send me a friend request, well the more the merrier. I think we can get quite a few converts if we plan it right. Some kind of facebook lilypond app would help - I'm thinking of a stripped down version of omet.ca (For those interested, it's easy to just put a pre--existing webpage/webapp into a facebook iframe - it's that simple). Just a thought. Great talking to you. Yes, we can surely do with some free music software pr. Great stuff also being done by http://scorio.org (and even http://etudeapp.com ). Also I've taken a small stride into the idea of a gui client for LilyPond (http://lilypond.org/schikkers-list ); we'll see when I find the time to develop that further. Greetings, Jan M. On Thu, Dec 9, 2010 at 2:49 AM, Jan Nieuwenhuizen jann...@gnu.org wrote: This is smart pr http://www.facebook.com/l.php?u=http%3A%2F%2Fmusescore.org% 2Fen%2Fabout%2Ftestimonialsh=cd3b2 also note they have 1500 fans on #fb today! Greetings, Jan -- Jan Nieuwenhuizen jann...@gnu.org | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl ___ lilypond-user mailing list lilypond-u...@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user -- Jan Nieuwenhuizen jann...@gnu.org | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Clarifying the 'padding alist-key
On 2010-12-09 16:15, Mark Polesky wrote: Mark Polesky wrote: 1) padding - the minimum required amount of vertical whitespace between two items, measured in staff-spaces. When available, skylines are used in the spacing calculation. 2) padding - the minimum required amount of vertical whitespace between the skylines of two items, measured in staff-spaces. Carl Sorensen wrote: I prefer 2. Trevor Daniels wrote: 2, but is skylines explained anywhere in the docs? If it is, it is not indexed. 2 for me, too. Interesting. I just assumed you'd both prefer #1, because IIUC most items don't have skylines for padding. Most? Anyway, after all, the main task of LilyPond still is typesetting /music/, not the headers. And for the spacing of staves, the skyline is both available and essential to understand, and should be prominently advertized. For example, do things like title/toplevel markups, lyrics, etc. have skylines? Markups: No, but - no skyline is a skyline, too, just a flat one... I consider this as a missing feature; I don't see the point why headers and toplevel markups should not have skylines. It's an annoyance when a single high note and a tempo mark at the beginning of a piece push the distance to the header, although only the composer and arranger (right side markup) are given. So, documenting the skylines sounds like the correct thing to me, but stating that top-level markup's ones are, well, somewhat unusual for now. (When available from #1 sounds simple and descriptive, though, but I'd like to have skyline the default.) Lyrics do have skylines, as well as chord names and IIUC basically everything you can enter in a score block. That is, everything /but/ top-level markups? (Though sometimes the estimations aren't that good as well; see the discussions recurring every now and then about refining skylines for hairpins, slurs or volta brackets, where the skylines are used for the intra-system spacing and extent estimation.) Trevor: when I `git grep' for skyline in the Documentation directory, I get nothing, so to answer your question: no, skylines are not explained anywhere in the docs. Well, the same point I mentioned in http://codereview.appspot.com/2316042/, right? I'm still not sure if it eases or complicates things to not use the term for the user, but in the end it's not too hard to understand to spare it out. And that it's lacking in the whole Documentation dir means that it's in absolutely no docs, right? That's bad - I can't see a point where this fits in the IR, but for some spacing tweaks it's important to have the real deal explained. Cheers, Alexander ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Need help with lilypond-2.12.3 documentation build failure
Hi, openSUSE:Factory lilypond is failing to build documentation since texlive was updated, I've added the updated texlive-bin package to the successful 11.3 build and it causes the same failure. I can't quite understand bibtex's use of /tmp in this failure : make[3]: Entering directory `/usr/src/packages/BUILD/lilypond-2.12.3/Documentation/bibliography' BSTINPUTS=. /usr/src/packages/BUILD/lilypond-2.12.3/scripts/build/out/bib2html -o out-www/colorado.html colorado.bib Invoking `bibtex /tmp/tmp8qyEcUbib2html' bibtex: Not writing to /tmp/tmp8qyEcUbib2html.blg (openout_any = p). I couldn't open file name `/tmp/tmp8qyEcUbib2html.blg' make[3]: *** [out-www/colorado.html] Error 1 make[3]: Leaving directory `/usr/src/packages/BUILD/lilypond-2.12.3/Documentation/bibliography' make[2]: *** [WWW-2] Error 2 make[2]: Leaving directory `/usr/src/packages/BUILD/lilypond-2.12.3/Documentation' make[1]: *** [WWW-2] Error 2 make[1]: Leaving directory `/usr/src/packages/BUILD/lilypond-2.12.3' make: *** [doc] Error 2 The entire build log can be viewed at : https://build.opensuse.org/package/rawlog?arch=x86_64package=lilypondproject=home%3Aplater%3Alilypondrepository=openSUSE_Factory Thanks Dave Plater ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Need help with lilypond-2.12.3 documentation build failure
On Fri, Dec 10, 2010 at 01:03:37PM +0200, Dave Plater wrote: Hi, openSUSE:Factory lilypond is failing to build documentation since texlive was updated, I've added the updated texlive-bin package to the successful 11.3 build and it causes the same failure. I can't quite understand bibtex's use of /tmp in this failure : make[3]: Entering directory Well, the first step is to isolate the problem. If you go to this directory: `/usr/src/packages/BUILD/lilypond-2.12.3/Documentation/bibliography' and then enter this command all as one line: BSTINPUTS=. /usr/src/packages/BUILD/lilypond-2.12.3/scripts/build/out/bib2html -o out-www/colorado.html colorado.bib then does it produce a .html file in out-www/ ? (oh, you need to create the out-www/ directory first) I'm not certain precisely why bibtex wants to write stuff to /tmp/, but it'll be a lot easier to debug the problem once you reduce it to a single command-line. Be aware that this part of the build process has changed in 2.13 and the upcoming 2.14 release. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Need help with lilypond-2.12.3 documentation build failure
On 12/10/2010 01:53 PM, Graham Percival wrote: On Fri, Dec 10, 2010 at 01:03:37PM +0200, Dave Plater wrote: Hi, openSUSE:Factory lilypond is failing to build documentation since texlive was updated, I've added the updated texlive-bin package to the successful 11.3 build and it causes the same failure. I can't quite understand bibtex's use of /tmp in this failure : make[3]: Entering directory Well, the first step is to isolate the problem. If you go to this directory: `/usr/src/packages/BUILD/lilypond-2.12.3/Documentation/bibliography' and then enter this command all as one line: BSTINPUTS=. /usr/src/packages/BUILD/lilypond-2.12.3/scripts/build/out/bib2html -o out-www/colorado.html colorado.bib then does it produce a .html file in out-www/ ? (oh, you need to create the out-www/ directory first) I'm not certain precisely why bibtex wants to write stuff to /tmp/, but it'll be a lot easier to debug the problem once you reduce it to a single command-line. Be aware that this part of the build process has changed in 2.13 and the upcoming 2.14 release. Cheers, - Graham I did that and it gives the same error, I made a local build and entered the directory : Arbuthnot:/usr/src/packages # pushd /usr/src/packages/BUILD/lilypond-2.12.3/Documentation/bibliography /usr/src/packages/BUILD/lilypond-2.12.3/Documentation/bibliography /usr/src/packages Arbuthnot:/usr/src/packages/BUILD/lilypond-2.12.3/Documentation/bibliography # BSTINPUTS=. /usr/src/packages/BUILD/lilypond-2.12.3/scripts/build/out/bib2html -o out-www/colorado.html colorado.bib Invoking `bibtex /tmp/tmp65e8GYbib2html' bibtex: Not writing to /tmp/tmp65e8GYbib2html.blg (openout_any = p). I couldn't open file name `/tmp/tmp65e8GYbib2html.blg' And the same result. Can you spot any change in the normal bibtex behaviour? Thanks Dave P ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Need help with lilypond-2.12.3 documentation build failure
Dave Plater dpla...@webafrica.org.za writes: I did that and it gives the same error, I made a local build and entered the directory : Arbuthnot:/usr/src/packages # pushd /usr/src/packages/BUILD/lilypond-2.12.3/Documentation/bibliography /usr/src/packages/BUILD/lilypond-2.12.3/Documentation/bibliography /usr/src/packages Arbuthnot:/usr/src/packages/BUILD/lilypond-2.12.3/Documentation/bibliography # BSTINPUTS=. /usr/src/packages/BUILD/lilypond-2.12.3/scripts/build/out/bib2html -o out-www/colorado.html colorado.bib Invoking `bibtex /tmp/tmp65e8GYbib2html' bibtex: Not writing to /tmp/tmp65e8GYbib2html.blg (openout_any = p). I couldn't open file name `/tmp/tmp65e8GYbib2html.blg' And the same result. Can you spot any change in the normal bibtex behaviour? Looks like bibtex does not want to write its log file to an absolute path by default any more. So bib2html will need to be changed accordingly. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Need help with lilypond-2.12.3 documentation build failure
On Fri, Dec 10, 2010 at 01:52:11PM +0100, David Kastrup wrote: Dave Plater dpla...@webafrica.org.za writes: bibtex: Not writing to /tmp/tmp65e8GYbib2html.blg (openout_any = p). I couldn't open file name `/tmp/tmp65e8GYbib2html.blg' And the same result. Can you spot any change in the normal bibtex behaviour? Looks like bibtex does not want to write its log file to an absolute path by default any more. So bib2html will need to be changed accordingly. Huh. Be aware that bib2html is no longer in git; we now use bib2texi. I expect that it would have the same problem, though. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Need help with lilypond-2.12.3 documentation build failure
On 12/10/2010 03:00 PM, Graham Percival wrote: On Fri, Dec 10, 2010 at 01:52:11PM +0100, David Kastrup wrote: Dave Plater dpla...@webafrica.org.za writes: bibtex: Not writing to /tmp/tmp65e8GYbib2html.blg (openout_any = p). I couldn't open file name `/tmp/tmp65e8GYbib2html.blg' And the same result. Can you spot any change in the normal bibtex behaviour? Looks like bibtex does not want to write its log file to an absolute path by default any more. So bib2html will need to be changed accordingly. Huh. Be aware that bib2html is no longer in git; we now use bib2texi. I expect that it would have the same problem, though. Cheers, - Graham I'm about to start packaging 2.13.42 for openSUSE but is there anything I can patch to get this build working again? Thanks Dave P ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Need help with lilypond-2.12.3 documentation build failure
On Fri, Dec 10, 2010 at 03:16:27PM +0200, Dave Plater wrote: On 12/10/2010 03:00 PM, Graham Percival wrote: Huh. Be aware that bib2html is no longer in git; we now use bib2texi. I expect that it would have the same problem, though. I'm about to start packaging 2.13.42 for openSUSE but is there anything I can patch to get this build working again? Well, you'd need to modify bib2html (and probably bib2texi) such that they work with your version of bibtex. The only thing those scripts do is some initial setup, and then call bibtex on the command-line. Basically, if you cannot run bibtex on the command-line, then that is a bibtex problem, not a lilypond build problem. If you look at the bibtex documentation, or mailing lists, or a CHANGES document, or something, I would hope that you could find some discussion about this. In the course of that discussion, hopefully somebody would give the command-line which is required to make bibtex work. Once you can run bibtex on the command-line, then we could discuss how you'd need to change bib2html. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Need help with lilypond-2.12.3 documentation build failure
On 12/10/2010 03:48 PM, Graham Percival wrote: On Fri, Dec 10, 2010 at 03:16:27PM +0200, Dave Plater wrote: On 12/10/2010 03:00 PM, Graham Percival wrote: Huh. Be aware that bib2html is no longer in git; we now use bib2texi. I expect that it would have the same problem, though. I'm about to start packaging 2.13.42 for openSUSE but is there anything I can patch to get this build working again? Well, you'd need to modify bib2html (and probably bib2texi) such that they work with your version of bibtex. The only thing those scripts do is some initial setup, and then call bibtex on the command-line. Basically, if you cannot run bibtex on the command-line, then that is a bibtex problem, not a lilypond build problem. If you look at the bibtex documentation, or mailing lists, or a CHANGES document, or something, I would hope that you could find some discussion about this. In the course of that discussion, hopefully somebody would give the command-line which is required to make bibtex work. Once you can run bibtex on the command-line, then we could discuss how you'd need to change bib2html. Cheers, - Graham I'll try the texlive-bin maintainer. Is this going to be a problem with 2.13.42 do you think? Thanks Dave P ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Need help with lilypond-2.12.3 documentation build failure
On Fri, Dec 10, 2010 at 04:19:59PM +0200, Dave Plater wrote: I'll try the texlive-bin maintainer. Is this going to be a problem with 2.13.42 do you think? I expect it would still be a problem. Or rather, if 2.13.42 works when 2.12.3 doesn't, then it would be an accident rather than on purpose. I can't remember fixing any bug related to this when I made bib2texi, but it's just possible that the general refactoring allowed us to avoid this specific problem. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 13.42 regtests
On 12/9/10 7:51 AM, Phil Holmes m...@philholmes.net wrote: I think the regtests for .42 are all OK. Many of the tab* tests are slightly different - .42 gives a little more space, and so the build regtest checker picks these changes up. See the attached image for an example of the actual changes. .42 shifts tab note heads slightly to the right, unless they have two digits, in which case they will be shifted significantly to the left. This is expected. Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LilyBuntu [don't read kainhofer.com!]
Hello, On 09/12/2010 15:32, Graham Percival wrote: Were you trying to run the autorun.sh , and not the other file that you mentioned ? I think the autorun.sh is the main file that you're supposed to run. Yes it is. I guess it depends if you are all 'point and clicky' or used to using CLI. The instructions in VBOX own manual tell you to run ./autogen.sh but as this is Ubuntu you have to run sudo ./autogen.sh then type the password and then the installer does everything for you, eventually you will be asked to press return to finish. Depending on what you are updating your VBOX tools from - you may be promoted to reboot. As a side note when you open VBOX main GUI it will check for any updates, if you do download the new VBOX binary, then stop the VM (you can shut it down or you can simply close the VM window and 'save state') and once the VM is not running or shutdown, close the VBOX main gui and run the update. The VBOX additions will detect on the next start up that they are from an older version and depending on what has changed between the VBOX update you have used now and had before you may have to run the ./autogen.sh again. If you use a windows VM it is easy as you can right click on the system tray and install the additions. This is probably waaay beyond the scope of the CG but I hope this helps someone. Also LilyBuntu is 9.0.4 and this version is no longer maintained by 'canonical' (?) so I no longer get prompted to update core components as I have them all installed. I only mention this because it is a while since I have reinstalled LilyBuntu and I seem to recall the ./autogen.sh script I run prior to make, had changed and did a lot more checking of components and apart from the dbflatex (?) version (which was slightly behind and generated a warning that I was told could be ignored), I cannot remember if I needed to apt-get any more core updates. But I didn't have any problems that I can remember. I use VBOX on Windows and on my Mac with LilyBuntu if anyone needs any advice or help and I also helped with the CG in parts on this too. James ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: @var in program's msgid/msgstr
On Thu, Dec 9, 2010 at 1:50 AM, Francisco Vila paconet@gmail.com wrote:
Hello. I am translating the program gettext file. What's the point of
emphasizing words with @var{} in msgid's? Is the output
(warning/errors etc) of the program to be processed by texinfo?
I think the intent is to *eventually* generate a list of
publicly-available functions for the Internals Reference, and some of
these functions use @var{} in their docstrings to indicate function
parameter names. There are inconsistencies here, in that some
docstrings are internationalized and some are not, and some public
functions don't have docstrings at all.
Also, note that many of these functions are LilyPond music functions
defined in .ly files, and the PO template generation does not notice
these docstrings. Perhaps this is a point we can address during GOP?
For example, in ly/music-functions-init.ly, you see
applyContext =
#(define-music-function (parser location proc) (procedure?)
(_i Modify context properties with Scheme procedure @var{proc}.)
but this string is not found in lilypond.pot.
I hope this clarifies things a bit for you.
Thanks,
Patrick
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LilyBuntu [don't read kainhofer.com!]
On Thu, Dec 09, 2010 at 03:33:02PM +0100, Reinhold Kainhofer wrote: Am Mittwoch, 8. Dezember 2010, um 19:58:58 schrieb Graham Percival: Ouch. Please do *not* read kainhofer. From time to time, the docs there stop updating. In this case, you're looking at old docs which I spent approximately 5 hours rewriting back in August. This is frustrating for everybody involved. Actually, I'm getting the results of the daily cronjob via mail, so I should notice as soon as compilation breaks one morning... Yes, you'll discover any compile *failures*. But our build system does not rebuild any manual unless the main file (in Documentation/*.te??) is touched. Since we only alter those files twice a year or so, there's lots of old docs on kainhofer. In particular, http://kainhofer.com/~lilypond/ajax/Documentation/contributor/ does not include CG 1.3 lilybuntu, which was added in cb1c621969fe36a13e474e1bc55647445f9f3ffe on 31 Aug 2010. Yes, our build system sucks. No, I'm not going to try to fix this particular problem. Yes, I'd be happy with a patch to fix it. No, I'm not certain that creating such a patch would actually be an ideal use of time, given all the other problems we have. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Need help with lilypond-2.12.3 documentation build failure
On Fri, Dec 10, 2010 at 6:40 AM, Graham Percival gra...@percival-music.ca wrote: On Fri, Dec 10, 2010 at 04:19:59PM +0200, Dave Plater wrote: I'll try the texlive-bin maintainer. Is this going to be a problem with 2.13.42 do you think? I expect it would still be a problem. Or rather, if 2.13.42 works when 2.12.3 doesn't, then it would be an accident rather than on purpose. I can't remember fixing any bug related to this when I made bib2texi, but it's just possible that the general refactoring allowed us to avoid this specific problem. Perhaps this is related? http://lists.gnu.org/archive/html/lilypond-devel/2010-01/msg00524.html The fix is here in master: http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=da009bcd6532ed1564440ddff73a1a92019d5420 Thanks, Patrick ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: make doc fails on git
On Thu, Dec 09, 2010 at 10:09:50AM -0700, Carl Sorensen wrote: I've got commit 16bdb67bb1ce1f52380b36e264869c2b61aa3553 I'm guessing that you fxied this in e7477, since git master looks fine to me in 1ba780. I just rebuilt everything from scratch with no problems. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [patch] Web: use existing png images instead of jpg.
On Thu, Dec 09, 2010 at 04:40:42PM +0100, Francisco Vila wrote: All these jpgs are currently causing 404 errors from lilypond.org. Patch included, can not push right now. Thanks, pushed. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
LSR down?
Can't seem to hit it from 'here' James ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
accidental-unbroken-tie-spacing.ly
I've downloaded and installed LilyBuntu and I've got the source with git, so I'm looking for a simple regtest to improve, to practice. I've come across accidental-unbroken-tie-spacing.ly To me, there are a number of errors. Apart from the fact that I'm not convinced by the word accidentaled , it claims that tied notes with accidentals cause reminder accidentals. I don't believe they do. We could modify the regtest to force a reminder with !. Before I go ahead and force the accidental and improve the description, could someone confirm that this would be a minor, but correct change? -- Phil Holmes Bug Squad ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: accidental-unbroken-tie-spacing.ly
On Dec 10, 2010, at 7:48 PM, Phil Holmes wrote: I've downloaded and installed LilyBuntu and I've got the source with git, so I'm looking for a simple regtest to improve, to practice. I've come across accidental-unbroken-tie-spacing.ly To me, there are a number of errors. Apart from the fact that I'm not convinced by the word accidentaled , it claims that tied notes with accidentals cause reminder accidentals. I don't believe they do. We could modify the regtest to force a reminder with !. Before I go ahead and force the accidental and improve the description, could someone confirm that this would be a minor, but correct change? Perhaps this is only a problem of the description. Comparing accidental-tie.ly and accidental-unbroken-tie-spacing.ly, one could theoretically use the same music (changing which notes should show accidentals) for both. If accidental-tie has the second measure on the same system (unbroken), there is no accidental, which is normal engraving practice. If accidental-unbroken-tie-spacing has the second measure on a different system (broken) there is an accidental. I always understood these two to demonstrate that: a) an accidental on a tied note is shown after a line break and b) a note tied from a note with an accidental (how's that for getting around accidentaled?) on the same system (unbroken) does not go wonky with the spacing. Perhaps the description should just omit the bit about the reminder accidentals. ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
PATCH: Doc: Various to LM and NR additions from lilypond-user email threads
Hello, http://codereview.appspot.com/3581041/ Have a good weekend. James ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Need help with lilypond-2.12.3 documentation build failure
On 12/10/2010 05:13 PM, Patrick McCarty wrote: On Fri, Dec 10, 2010 at 6:40 AM, Graham Percival gra...@percival-music.ca wrote: On Fri, Dec 10, 2010 at 04:19:59PM +0200, Dave Plater wrote: I'll try the texlive-bin maintainer. Is this going to be a problem with 2.13.42 do you think? I expect it would still be a problem. Or rather, if 2.13.42 works when 2.12.3 doesn't, then it would be an accident rather than on purpose. I can't remember fixing any bug related to this when I made bib2texi, but it's just possible that the general refactoring allowed us to avoid this specific problem. Perhaps this is related? http://lists.gnu.org/archive/html/lilypond-devel/2010-01/msg00524.html The fix is here in master: http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=da009bcd6532ed1564440ddff73a1a92019d5420 Thanks, Patrick Thanks all, the patch did the trick. Regards Dave Plater ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LilyBuntu [don't read kainhofer.com!]
2010/12/10 Graham Percival gra...@percival-music.ca: Yes, you'll discover any compile *failures*. But our build system does not rebuild any manual unless the main file (in Documentation/*.te??) is touched. Since we only alter those files twice a year or so, there's lots of old docs on kainhofer. In particular, http://kainhofer.com/~lilypond/ajax/Documentation/contributor/ does not include CG 1.3 lilybuntu, which was added in cb1c621969fe36a13e474e1bc55647445f9f3ffe on 31 Aug 2010. Why not touch everything that is touchable (files, I mean) and force a complete compiling, daily? What does GUB do to make a release? Whatever it does to obtain a new set of manuals, any daily snapshot should do the same. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LilyBuntu [don't read kainhofer.com!]
On Sat, Dec 11, 2010 at 12:21:42AM +0100, Francisco Vila wrote: 2010/12/10 Graham Percival gra...@percival-music.ca: Yes, you'll discover any compile *failures*. But our build system does not rebuild any manual unless the main file (in Documentation/*.te??) is touched. Since we only alter those files twice a year or so, there's lots of old docs on kainhofer. Why not touch everything that is touchable (files, I mean) and force a complete compiling, daily? If you want to force a complete compile, then I recommend removing the build directory entirely and starting from scratch. This is very easy with an out-of-tree build. What does GUB do to make a release? I completely wipe the build dirs. Whatever it does to obtain a new set of manuals, any daily snapshot should do the same. No. The docs on kainhofer.com are not our official docs. It is a private server which Reinhold graciously makes available. Compiling the docs from scratch requires a fair amount of resources, ranging from CPU power to disk life (by using read/writes) to electricity. I agree that any official daily snapshot should build from scratch. But I don't think it's worth the resources it would take. A daily doc build was fantastic during GDP, but these days the docs don't change all that rapidly, and all doc contributors can build the docs themselves (mostly with lilybuntu). Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LilyBuntu [don't read kainhofer.com!]
2010/12/11 Graham Percival gra...@percival-music.ca: Whatever it does to obtain a new set of manuals, any daily snapshot should do the same. No. The docs on kainhofer.com are not our official docs. It is a private server which Reinhold graciously makes available. Compiling the docs from scratch requires a fair amount of resources, ranging from CPU power to disk life (by using read/writes) to electricity. I agree that any official daily snapshot should build from scratch. But I don't think it's worth the resources it would take. A daily doc build was fantastic during GDP, but these days the docs don't change all that rapidly, and all doc contributors can build the docs themselves (mostly with lilybuntu). If it's for the planet, it is obvious that a single daily snapshot takes far less resources than many snapshots made by contributors. Granted, other would pay for it, so that it's free for me. But the whole amount is what counts :-) -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LilyBuntu [don't read kainhofer.com!]
On 12/10/10 5:21 PM, Francisco Vila paconet@gmail.com wrote: 2010/12/11 Graham Percival gra...@percival-music.ca: Whatever it does to obtain a new set of manuals, any daily snapshot should do the same. No. The docs on kainhofer.com are not our official docs. It is a private server which Reinhold graciously makes available. Compiling the docs from scratch requires a fair amount of resources, ranging from CPU power to disk life (by using read/writes) to electricity. I agree that any official daily snapshot should build from scratch. But I don't think it's worth the resources it would take. A daily doc build was fantastic during GDP, but these days the docs don't change all that rapidly, and all doc contributors can build the docs themselves (mostly with lilybuntu). If it's for the planet, it is obvious that a single daily snapshot takes far less resources than many snapshots made by contributors. Granted, other would pay for it, so that it's free for me. But the whole amount is what counts :-) Yes, but we contributors don't do daily builds. We do builds when we make changes (and we *need* to do builds to verify they work before we submit changes). Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LSR down?
On 10 December 2010 19:15, James james.l...@datacore.com wrote: Can't seem to hit it from 'here' LSR is up 'here' (and now), and not just here. http://downforeveryoneorjustme.com/http://lsr.dsi.unimi.it/ Cheers, Xavier -- Xavier Scheuer x.sche...@gmail.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LilyBuntu [don't read kainhofer.com!]
Am Samstag, 11. Dezember 2010, um 00:38:54 schrieb Graham Percival: On Sat, Dec 11, 2010 at 12:21:42AM +0100, Francisco Vila wrote: 2010/12/10 Graham Percival gra...@percival-music.ca: Yes, you'll discover any compile *failures*. But our build system does not rebuild any manual unless the main file (in Documentation/*.te??) is touched. Since we only alter those files twice a year or so, there's lots of old docs on kainhofer. Why not touch everything that is touchable (files, I mean) and force a complete compiling, daily? If you want to force a complete compile, then I recommend removing the build directory entirely and starting from scratch. This is very easy with an out-of-tree build. Unfortunately, it seems that an out-of-tree build does not work for the docs, only for the binaries. In particular: -) Documentation/out-www/version.itexi is not created, so lilypond-book fails -) Later on, lilypond-book does not find some included *.itely files: All snippets are up to date... Compiling /home/lilypond/build/Documentation/out-www/common-macros.texi... /home/lilypond/build/Documentation/out-www/common-macros.texi is up to date. Processing include: pitches.itely lilypond-book.py: error: file not found: pitches.itely Cheers, Reinhold -- -- Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
