Re: GOP2-2b - Stable 2.16.x releases (dictator) (probable decision)
Il giorno mer, 01/08/2012 alle 20.51 +0100, Graham Percival ha scritto: > I was particularly thinking of the download links and links to > docs (on both the Downloads page and the Development page). That > needs to do build number -> python -> texinfo macros -> html. But > at least it's fully debuggable just with "make website", without > bringing in the hour of a normal "make doc". Oh, I see. I thought the scripts building this (e.g. scripts/build/create-weblinks-itexi.py) were already looking for actual release numbers instead of assuming "1". > I'm not sure offhand how to get the build number, since we don't > put it into VERSION. Maybe check the http directory and grab the > filename if there's an internet connection, or else not default to > -1 ? As for "make doc", could GUB set up an environment variable? As for "make website", we could use something similar to what was used for the old website on a separate Git branch. > > IMHO patch level numbers are cheap, as it doesn't often happen to > > release twice within two or three days. > > ok, I suppose we could just not bother with this, then. It appears from this discussion that this issue is not so urgent, so I've added a comment to http://code.google.com/p/lilypond/issues/detail?id=1004 Please correct me if my comment there is wrong. Best, John ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GOP2-2b - Stable 2.16.x releases (dictator) (probable decision)
Il giorno mer, 01/08/2012 alle 18.08 +0100, Graham Percival ha scritto: > Hmm. I can't answer this directly, but I'll pass along my > considerations: > > - if you try to compile GUB on debian unstable (or any other > recent distro), you will likely encounter odd compile failures. > These are important to fix at some point in time (otherwise we'd > be stuck GUB on ubuntu 10.04 only), and require a great deal of > knowledge of compilers and searching for solutions online. > OTOH, it might just work "out of the box" in which case it'll > just take 6-12 hours and then be working. With my Fedora installation on that Core 2 Duo (x86_64), GUB Python program has screwed up dependencies (it missed a lot of them) in a consistent way across different Fedora versions, and when I reported it I got not clue on debugging the intricated Python code of GUB, so I think my next attempt at building GUB will be a chrooted Debian stable. Now I've freed my main machine from lilypond-patchy-staging, I can more easily build a GUB in background while doing other things, reporting how it progresses and asking for help if needed. > - I think that supporting build numbers will be an easier > introduction to version number handling in GUB and our docs than > jumping straight into 4-tuples. The first step is to make it > work in "make website", which is infinitely easier than trying > to do anything in GUB. This is a relatively easy thing to fix, > so it might make sense to leave it for a relative beginner... > OTOH, the bug has existed for two years, so might as well tackle > it now. I guess that if we want the release number in "make website", we want it in HTML footers and manuals, don't we? > Also, David is quite likely to want to use build > numbers if they are available. > (whereas I'm happy to say "screw users" or "screw version > numbers" and either not bother updating with -2 if there's a > serious problem, or else bump to .x+1 one day after a .x > release; neither of those options are particularly ideal for a > stable branch) IMHO patch level numbers are cheap, as it doesn't often happen to release twice within two or three days. Best, John ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GOP2-2b - Stable 2.16.x releases (dictator) (probable decision)
Il giorno mer, 01/08/2012 alle 19.26 +0200, David Kastrup ha scritto: > Build numbers are not all that relevant for _us_ as far as I can tell. > They distinguish different versions compiled from the _same_ canonical > source (so they don't belong into our VERSION file at any rate). > Changes may be updates of the dependencies, of the compiling platform, > of the downstream patches. > > In our case, they would become relevant only when GUB gets updated and > we require a rerelease from otherwise unchanged sources because of that. We have some history of release tags used in place of bumping patch level in version number: http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=shortlog;h=refs/tags/release/2.12.3-2 That said, such goofs like that one I was involved in regarding documentation translations is less likely to happen with staging mechanism, a different implementation of "make dist" (I'm testing a patch, see dev/jmandereau if you're impatient), and you controlling the commits that will go in stable/2.16. John ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GOP2-2b - Stable 2.16.x releases (dictator) (probable decision)
Il giorno mer, 01/08/2012 alle 15.52 +0100, Graham Percival ha scritto: > Regardless of the question of having a tuple of four values, it > would be nice to support build numbers, i.e. 2.15.43-2: > http://code.google.com/p/lilypond/issues/detail?id=977 > > This definitely requires work in both lilypond git and GUB git. I'm confident we don't want to add support for tuples of four values or release tags in convert-ly, but website generation and docs generation (Texinfo macros and HTML footers) need work. Do you prefer that I spend effort on building GUB for the coming week or rather make patches on lilypond.git only? John ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GOP2-2b - Stable 2.16.x releases (dictator) (probable decision)
Il giorno mer, 01/08/2012 alle 15.21 +0200, David Kastrup ha scritto: > Graham Percival writes: > > On Wed, Aug 01, 2012 at 02:37:58PM +0200, David Kastrup wrote: > >> If it is non-operative, it should be either made operative or removed. > >> There is no point dragging it along as purely dead weight we should not > >> be using. > > > > Sure, patches appreciated. > > You know that this comes across as "In my opinion nobody but the foolish > person asking for this should think of working on that problem."? I am > staking out the requirements I need to get the appointed job done. > Unless you have some reasonable suggestions how to get around those > requirements, I see little point in discouraging others from helping > with them. +1 I'm sometimes slow to react (up to one week for making a patch), but I'm willing to help with version number management in the build system if this definitely appears to be the route to go with. On the minus side, I've been too lazy so far to get GUB to build on my main computer, but this laziness is not unrecoverable :-) > > I'm missing something. What's wrong with this scenario: > > - I release 2.15.42 today or tomorrow. > > - you branch stable/2.16 from that. > > - in a week I release 2.17.0. > > - you do whatever you want with 2.15.43, 2.15.44, etc, until you > > reach 2.16.0. Other than probably having no syntax changes > > because I really don't know how that can be juggled. > > There will be no syntax changes in the 2.16 branch, at least not of the > convert-ly kind (one reasonably established syntax to a different > intended one). In Graham's scenario above, syntax changes could be handled by applying them to both stable/2.16 and master, as long as the convert-ly rules can be inserted in 2.17 series between syntax changes in 2.15.42 and those present only in 2.17 series. > >> 2.15.95 would presumably protest against snippets already being at > >> 2.16.0. > > > > The final change of version numbers it the last thing we've done > > in the past, and just tested on my local machine with make doc. > > Hm. At any rate, it seems strange to have 2.17.0 released and no > recognizable disruption in the 2.15 release series while 2.16 is not > finished. It seems strange indeed, but explaining/referencing this in the News and Changes and CG (and maybe Usage), and contacting packagers to tell 2.15 releases are RCs to be included in alpha releases of distributions could solve strange feelings on this version numbers playing while saving us from messing up with the build system (including website making) and GUB. Best, John ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
lilypond.org is mute
Hi Jan, A French lilyponder reported one hour ago on the French list that lilypond.org sends empty contents for HTML pages, both the home page and a few known good URLs; note that I tested also some obviously wrong URLs and they all returned 404 errors. It seems that there is some permissions or Apache configuration issue. Best, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Creating a comparison of several variants of unmettered chant
Le mardi 09 février 2010 à 07:07 -0800, Jiri Zurek (Prague) a écrit : > The scaled durations do not offer a solution, just a workaround. Lilypond > still attempts to "count" the beats, aligning vertically beat after beat. > What I would like to achieve is to force Lilypond not to count beats at all. > Rather, to align vertically certain "bits of music" which I mark clearly > somehow, for example by the "|" sing (as in parallel music). Is there such a > possibility? Yes, by writing a music function in Scheme which takes as an argument all the music expressions of individual voices, then insert skips or duration mutlipliers according to such markers you mention. That said, I'm not sure how to encode such a marker in a form that should be recognizable by the music function code that recurse into music expression and that still makes individual voices valid music expressions. AFAIK there is no simpler mean to do this automatically. It might be nice to be able to have ways to synchronize staffs or voices (even with heterogenous material mixing standard notation staffs and other stuff like curves) like what you expect, like the Sheet object in OpenMusic, but this would be much much more involved. Good luck, John signature.asc Description: Ceci est une partie de message numériquement signée ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond as MediaWiki extension does not print in Extension:Collection
Le jeudi 28 janvier 2010 à 15:48 +0100, Oscar van Dillen a écrit : > " You can install and use this extension in your wiki, but it is currently > not available in Wikipedia. Many people would love to use this extension > in Wikipedia and other large-footprint wikis that they have no control > over. However, in its current form, this is unfortunately impossible due > to security concerns. This is not a reason not to support LilyPond processing as a option that is switchable by a configuration file accessible only to the website administrator, which would be disabled by default. > is this correct, that lilypond has this "security issue" as stated; > and is it possible " to make the program hang indefinitely"? Adding to Kieren's example, think that LilyPond user interface is a programming language, so it is hard to avoid these problems, that's the workaround that consists of limiting CPU and memory usage is recommended. Even with normal use of such an extension, you need much CPU power and free memory, which is surely not available on many servers running MediaWiki. Best, John signature.asc Description: Ceci est une partie de message numériquement signée ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond as MediaWiki extension does not print in Extension:Collection
2010/1/27 Oscar van Dillen : > on my website I found that Lilypond as MediaWiki extension does not print > music notation, just code, to the pdf in Extension:Collection > http://www.mediawiki.org/wiki/Extension:Collection > Lilypond does work fine when using "printable version" such as can be seen > here http://www.oscarvandillen.com/Triad?printable=yes > should I rather tell the collection programmers at > http://www.mediawiki.org/wiki/Extension:Collection/Wishlist Yes, please. If that extension shows only the LilyPond source code of snippets but the normal page view and the printable view show these snippets processed and converted to PNG, it surely means that LilyPond is not called to process these snippets from Extension:Collection. By the way, for a decent printing quality, the PDF generation should not be left to the user browser but should be done on the server side (using PDF snippets generated by LilyPond), like what openstreetmap.org does. This regards standard printable view as well as the extension Collection. Best, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [2.13.11-1] lilypond-book: duplicate filename but different contents of orginal file
Le dimanche 24 janvier 2010 à 18:36 +0200, Dmytro O. Redchuk a écrit : > Well, i believe this mean that i use the same music fragment in several > different places. > > If so, i believe that these warnings do not mean that i'm getting any > troubles with that piece(s). > > If so... Sorry for the noise :O) > > 2.12 does not produce such warnings, that's why i was getting "to feel > unstable". You're right that this warning and the printed diff mean nothing more than the fact you use one snippet twice, and that LilyPond is called only once by lilypond-book to compile it; these warnings are usually harmless, but we have suspected hash collisions, that's why we introduced some code to actually catch occurrences. For 2.14 I want to make lilypond-book silence out this warning in case the two snippets differ only by source location. You're welcome for this kind of noise :-) Best, John signature.asc Description: Ceci est une partie de message numériquement signée ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond-book question
Le jeudi 07 janvier 2010 à 10:47 +0100, Mats Bengtsson a écrit : > > What do all (pdf)(La)TeX users on this list think about making > > lilypond-book implcitly set latex-program option to 'pdflatex' if the > > format is 'latex' and --pdf option is set? > > > This definitely makes sense. Since I have never explicitly specified a > pdftex option to any package, I haven't thought about the problem, but > it's obviously better if lilypond-book uses pdflatex when it internally > figures out the line width if it knows that that's what the user will > use to process the full document. Done, John signature.asc Description: Ceci est une partie de message numériquement signée ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond-book question
James, sorry for having missed this email, but it surely has a missing header that prevented my mail client to show it in the same thread as other messages. Le mardi 05 janvier 2010 à 10:53 +0100, James Bailey a écrit : > I realise the problems: > The correct command should be lilypond-book --latex-program=pdflatex > --pdf myfile.lytex > pdflatex myfile.tex What do all (pdf)(La)TeX users on this list think about making lilypond-book implcitly set latex-program option to 'pdflatex' if the format is 'latex' and --pdf option is set? > I would send a patch, but I had a really bad experience last time I > tried to make a patch. Can someone make this change? Sure, but if everybody agrees on making the change to lilypond-book, the docs won't need to be changed. Best, John signature.asc Description: Ceci est une partie de message numériquement signée ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond-book question
Le mardi 05 janvier 2010 à 10:35 +0100, James Bailey a écrit : > Firstly, lilypond complains that it doesn't understand this extension. > lilypond-book: error: cannot determine format for: lily-book- > sample.pdftex This is normal: according to "4.5 Filename extensions" at http://lilypond.org/doc/v2.12/Documentation/user/lilypond-program/Filename-extensions you must specify --format command line option if you don't use a filename extension recognized by lp-book. Best, John signature.asc Description: Ceci est une partie de message numériquement signée ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond-book question
Le mercredi 06 janvier 2010 à 23:04 +0100, Mats Bengtsson a écrit : > Quoting James Bailey : > > pdflatex always complains if I don't have it there > > That's weird! The graphicx package should automatically detect if you > are using pdflatex or latex and choose the appropriate driver. Agreed. I can't remember if pdflatex issues any warning if I don't specify [pdftex], but it always produced correct output without this option (with TeXlive 2008 and 2009). James, which TeX distro do you use? > Explicitly specifying this option is a bad idea in general. Yes, and in particular it makes lilypond-book fails (see below the explanation). > (Note that > this has nothing to do with lilypond-book per se). It has actually something to do: lilypond-book calls latex on the preamble of the .lytex document in order to determine the line width (IIRC, and/or some paper-related metrics anyway), hence the failure of latex James reported in his first email if the input file extension is .lytex. To work around this, best is to remove [pdftex] option from the .lytex, but it might work to set lilypond-book command line option --latex-program=pdflatex. James, if you sum up the issues raised in this thread into one or two paragraphs, we'll consider adding them to a section 'Known issues and warnings' in lp-book docs. Best, John signature.asc Description: Ceci est une partie de message numériquement signée ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: convert-ly can't cope with accented filename
Le mardi 05 janvier 2010 à 08:03 +1100, Nick Payne a écrit :
> Try to run convert-ly on a file with an accented name and I get the
> following:
>
> > convert-ly --edit "/home/nick/lilypond/Bésard_preludio.ly"
> convert-ly (GNU LilyPond) 2.13.10
> Traceback (most recent call last):
>File "/usr/local/lilypond/usr/bin/convert-ly", line 337, in ?
> main ()
>File "/usr/local/lilypond/usr/bin/convert-ly", line 331, in main
> do_one_file (f)
>File "/usr/local/lilypond/usr/bin/convert-ly", line 233, in do_one_file
> ly.stderr_write (_ ("Processing `%s\'... ") % infile_name)
>File
> "/usr/local/lilypond/usr/share/lilypond/current/python/lilylib.py", line
> 59, in stderr_write
> encoded_write (sys.stderr, s)
>File
> "/usr/local/lilypond/usr/share/lilypond/current/python/lilylib.py", line
> 51, in encoded_write
> f.write (s.encode (f.encoding or 'utf_8'))
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 33:
> ordinal not in range(128)
This is a bug, the real question for fixing it is: how to figure out the
encoding of the filesystem in Python?
Thanks for the report,
John
signature.asc
Description: Ceci est une partie de message numériquement signée
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: No Work!
Le mercredi 16 décembre 2009 à 18:56 -0600, Tim McNamara a écrit : > I don't buy the generalized Unix notion that "doing things the hard > way is a virtue." Where do you get this notion from? Note that the most popular operating systems except Microsoft ones are Unix-based. It's not doing things the hardway, it's doing things to make it easy to reply to the sender only, taking into account uncommon situations as well, like users who need to indicate a reply-to address different from the expedition address. Well, I don't know why I repeat an argument exposed in the document I previously linked. > Literally every other mailing list in which I > participate sets the Reply-To header to the list. It works better. > This one is the anomaly and routinely results in e-mails being sent > to individuals, not to the list, resulting in "please send all e- > mails to the list" posts, etc. Sorry, but you haven't exhibited so far a concrete ground in favor of setting the Reply-To. A sophism ad populum like this will not convince me, and it might not convince the administrator of this list either. Best, John signature.asc Description: Ceci est une partie de message numériquement signée ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: No Work!
Le mardi 15 décembre 2009 à 20:20 -0600, Tim McNamara a écrit : > Wouldn't it be simplest to set the Reply-To header to the list? Then > all replies go to the list by default. No. For good reasons about this, see http://www.unicom.com/pw/reply-to-harmful.html Best, John signature.asc Description: Ceci est une partie de message numériquement signée ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: No Work!
Le mardi 15 décembre 2009 à 12:39 +0100, Federico Bruni a écrit : > [OT] > I recently realized that a good practice is not using Cc, unless you > have to reply to a person who is not subscribed to the mailing list. > The problem is that not all email clients are able to handle the reply > well. > > For those who use Thunderbird, I suggest to use version 3, which add a > Reply to List button. List members other than adminsitrators (and maybe moderators) can't exactly check whether an email address is subscribed to a LilyPond list, so unless you reply to a developer or user who send so many messages to the list that he must be subsribed, please make sure the individual address you reply to in Cc or To fields, that is, use "Reply to all", not "Reply to list". Best, John signature.asc Description: Ceci est une partie de message numériquement signée ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Wanted: documentation editor
Le vendredi 20 novembre 2009 à 14:56 +, Graham Percival a écrit : > 1) cd Documentation; make doc > 2) go cook dinner or read slashdot or catch up on emails or > whatever > 3) if it fails, complain on -devel. If it succeedes, then commit > the changes you want to test. > 4) touch Documentation/changed-manual.tely > 5) cd Documentation; make doc > 6) go cook dinner or read slashdot or catch up on emails or > whatever > 7) if it fails, complain to the person who sent you the patch. ... and add a few minutes for 8) quickly skim through the output (HTML, PDF, and/or Info) to see whether the result looks good; this is not necessary all the time, e.g. it's not absolutely necessary when you edit only plain text. Best, John signature.asc Description: Ceci est une partie de message numériquement signée ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond-book on osx 10.4
Le mercredi 28 octobre 2009 à 19:34 +0100, James E. Bailey a écrit : > downgrading to python 2.4.6 solved the problem and lilypond-book works > perfectly now. Whom do I talk to to have this updated in the > distributed binary? Or is this not a feasible option because 10.5 and > 10.6 don't have this problem? Downgrading Python is a workaround, but it's not a solution. Does replacing from md5 import md5 by from hashlib import md5 in /Users/jamesebailey/Applications/LilyPond_devel.app/Contents/Resources/bin/lilypond-book help? Best, John signature.asc Description: Ceci est une partie de message numériquement signée ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: website so close, and yet so far
Le jeudi 29 octobre 2009 à 11:04 +0100, Valentin Villenave a écrit : > Wow, is this normal: > > http://lilypond.org/doc/v2.13/Documentation/ > > This link points to the non-officially-published website's homepage??? IMO it's too early to replace the old documentation index with the new website, but I've been so idle in docs building lately that I feel my voice won't count. Best, John signature.asc Description: Ceci est une partie de message numériquement signée ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: polyphony in tablature
Le vendredi 21 août 2009 à 21:53 +0100, Graham Percival a écrit : > Ah, I was unclear. It checks for texi2html (oops, I meant to say > that above!), but not the version number. Does it really on your system?! Please test and/or check before claiming this. > Most people have 1.78, > whereas we need 1.82. configure should issue a warning if texi2html < 1.82 is installed. Bug reports are welcome if this is not the case for you. Cheers, John signature.asc Description: Ceci est une partie de message numériquement signée ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP and (Learning Manual and Notation Reference)
Le vendredi 21 août 2009 à 08:54 +0100, Graham Percival a écrit : > LM 5 is being moved into the AU, What's the rationale for this? I must have missed in some discussion on the lists, but I couldn't find it in Git commit message as I might have expected. Cheers, John signature.asc Description: Ceci est une partie de message numériquement signée ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: polyphony in tablature
Le vendredi 21 août 2009 à 08:49 +0100, Graham Percival a écrit : > You're using texinfo < 1.8.2. Yes, it would be nice if the > configure script checked for the doc-building programs (this > request is already on the tracker)... It does, but this check is not enforced, only a warning is printed at the end of configure output. Many other documentation dependencies are not checked by configure, though. > but since John is working on > sconscript anyway, I'm not sure SCons is the best choice. I've been looking at Waf documentation too, this might be a better alternative for performance issues, as you or somebody else have already mentioned. > there's not much point fiddling with autoconf. Agreed. Cheers, John signature.asc Description: Ceci est une partie de message numériquement signée ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Minor releases?
Le lundi 17 août 2009 à 16:20 -0400, David Raleigh Arnold a écrit :
> You do a great job summarizing the minor versions of the development
> versions, but there is nothing in news-gmane-lilypond.devel about stable
> minor changes.
The only changes in stable releases so far have been bugfixes (that can
listed for each release at our Google tracker) and documentation
improvments backported from development branch (which have been only
detailed in git commit messages so far).
> There is no CHANGES document in my lilypond tree.
There will be Documentation/changes.tely in next release of the source
tree, which will show as Documentation/changes.{html,pdf} in the docs
tarball and web site. This document was previsously named NEWS.
> What
> is a git log?
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=log;h=refs/heads/master
It's only intended to be read by developers, contributors and curious
people.
HTH,
John
signature.asc
Description: Ceci est une partie de message numériquement signée
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Minor releases?
Le dimanche 16 août 2009 à 14:34 -0700, Graham Percival a écrit : > On Sun, Aug 16, 2009 at 11:48:53AM -0400, David Raleigh Arnold wrote: > > I don't see any straightforward way of seeing a changelog or > > anything which tells the differences between minor releases. > > The git log messages. And the news item and lilypond.org, which is also sent by email to info-lilyp...@gnu.org. > There's a NEWS/Changes document that shows any major changes. > Other than that, the only location are the git log messages. No, > we're not going to add a third source of info about such things; > we already don't have enough people working on administration as > it is. I'm thinking of generating automatically (like translations status) a documentation Change Log that would report new, changed and removed sections, including links to the relevant sections (yet another application of a Texinfo parser). I wouldn't be surprised if this could improve review of doc changes, as even users with almost no time available could give feedback and suggest corrections. Best, John signature.asc Description: Ceci est une partie de message numériquement signée ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: proposal for doc+web sources
Le samedi 18 juillet 2009 à 04:46 -0700, Graham Percival a écrit : > There was a request to add the version numbers to pdf files, i.e. > lilypond-2.13.4.pdf > lilypond-notation-2.13.4.pdf > > If this is easily done in the makefiles, then I think it might be > a good idea -- but if it's tricky to do it, especially while > maintaining cross-references, then by all means let's not bother. > I think that as long as the doc tarball has a version number on > it, there won't be confusion about this. It is doable but it's yet another boring task; as users who want to store manuals in several versions can easily put them in some directories without losing any functionality, I'm not interested in doing this. If somebody can convince me it's so useful *and* is willing to pay for it, I might change my mind. John signature.asc Description: Ceci est une partie de message numériquement signée ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: new website draft 5: help wanted, I mean it
2009/7/11 Tim McNamara : > I think there'd be more contributors if > contributing was a simple process (and not so Linux-centric): installing git > and all its myriad dependencies, learning texinfo, etc. I simply don't have > time for all that. I'm happy to write text, revise text, proof-read etc. > for the Web site and the docs, but I'd submit anything in text or HTML. I understand your point, as I feel a lot of potential translators have been scared away because of this, but there is nothing much we can do until we manage to test, install and develop web interfaces to the version control system that offer file editing and submission facilities for people that can't or don't want to learn using command-line tools or fetch all the sources. Best, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Dutch download page (was: lilypond 2.13 download)
2009/7/7 Graham Percival : > It involves the build system, just like the site in English. > odd python files, etc. I admit that these scripts are little or not documented. > How will it be different from the doc translations? It's all > texinfo files. In fact, these texinfo files don't have any > @lilypond sections, so wouldn't it be even easier? What would be easier? The stalled files issue is orthogonal with switching to Texinfo. Best, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Dutch download page (was: lilypond 2.13 download)
Hi guys, Le samedi 04 juillet 2009 à 09:37 -0700, Graham Percival a écrit : > This is also true of the site built from git, so it's not a > webserver issue. There has never been any file named nl/install/index.html in the web site source tree, and "make" does not generate any file named install/index.nl.html on my box, so install/index.nl.html that is actually present on lilypond.org must be a stalled file; could you remove it from lilypond.org manually? AFAIK the site build scripts never delete stalled files. > Anybody involved in the translations could > investigate (the translation infrastructure is too complicated for > me), It isn't that complicated, but maybe it's easier (or more motivating) to understand for non native English-speaking people. > or we could just wait until the next version of the webpages I doubt it's worth translating install/index.html in Dutch just before the new web site is brought online. > (where things should be simpler). I'm not sure about this either :-P John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: new website: draft 2.5, resolved
Le jeudi 25 juin 2009 à 03:50 -0700, Graham Percival a écrit : > Good points about -devel and bug-. IMO if we don't advertize > info-lilypond, we should junk that list. :) I guess the email medium is preferred, or at least more used, by some people than RSS, and this puts very little overhead on the release announcer. Speaking of, I don't claim that announcing releases should be exclusively done by the release meister, but have you realized that last release news item is three months old and is going to disappear from the list on the home page? Even if I don't know how reliably I'll be connected to the internet in July and August (this means, I'm not sure to have more than 1 hour of free connection time every day, but I won't be completely offline for more than four consecutive days), I consider volunteering again to write news items, giving more credit to the huge work done on GUB than I previously did, starting from next Tuesday. > ... I'm not arguing that we /shouldn't/ get rid of info. The > current webpage supports RSS, so if we dump the news items into > RSS, then people could get their instant notifications that way. They can normally already do, but there are buglets in XML formatting of our RSS feed that prevent Firefox from displaying it, see http://feedvalidator.org/check.cgi?url=http%3A%2F%2Flilypond.org%2Fweb% 2Flilypond-rss-feed.xml We were reported errors with Firefox months ago, but I didn't think about using a validator at that time, so overlooked the errors by lack of XML/XHTML knoweledge. Best, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: odd configure error
James E. Bailey a écrit : Am 25.03.2009 um 14:41 schrieb Graham Percival: Nothing; they come from exactly the same source. The version in the AU is going to die soon, where "soon" means "within 4 months". So then why the difference? I should think a one line command to get the source is easier and has a smaller margin of error than four lines. Which release/Git revision of the docs are you referring to? John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: odd configure error
James E. Bailey a écrit : I'm having a configure error, and I don't know how to solve it. I get this: ERROR: Please install required programs: /Users/lilydev/bin/fontforge >= 20050624 (installed: .fontforge 20080927) What does 'which fontforge' and '`which fontforge` --version' say? Could you quote the relevant part of config.log about fontforge check? There might be some problem with library path too. Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Good luck, Valentin
Jonathan Kulp a écrit : Francisco Vila wrote: Cross fingers, today is the premiere of Valentin's "the LilyPond Opera" in Montpellier. Success! The name is "Affaire étrangère"; how would you translate it, Valentin? :-) All right! Can't wait to hear how it goes. Good luck! IIRC it should have started at 15.00 CET, so the premiere is most probably finished. I hope this was a great success and the two other will go well too. Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: scheme - notes as variables
Hello Rob, Rob Canning wrote: i was trying to do it using scheme just because i thought learning to do this kind of thing in scheme would help me with other aspects of lilypond in general - perl looks neat though "the swiss army chainsaw of languages" i heard it refered to as :)- Using simple regexp substitution with Perl, Python or whichever scripting language you like is quite fragile, because regular expressions alone are not enough to parse LilyPond input format. maybe scheme is the wrong tool for the job? Currently Scheme is the only way to do it cleanly. Best would be implementing lambda calculus in ly language itself; I hope it's possible with writing a few music functions in Scheme. People at the GRAME in Lyon have already thought about lambda calculus usage in music notation, their articles is a good starting point for implementing these ideas in LilyPond. I don't have time to do this myself before March, though. Best, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Diatonic/modal transposition function (John Mandereau)
Stefan Thomas a écrit : Dear John, I tried now Your key-diatonic tranposition, but, in the below quoted snippet, it doesn't work. I get the error message: programming error: moving backwards in time Hello Stefan, I can reproduce this error and I get strange output (staves with only the staff symbol printed and nothing else), and slightly modifying the example results in a segfault. keyDiatonicTranspose is not stable, I recommend not using it until the bug or limitation behind this issue has been fixed. I'll try producing a minimal example to add in the bug tracker (hopefully with a function simpler than keyDiatonicTranspose). Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Long compilation times
Valentin Villenave a écrit : I'm running a 64-bits distro on a Pentium i7 with 6GB of Ram. (I had 3GB, but my opera wouldn't compile at less than 4). I have 4GB, and with a little swapping I can build it. If it needs to swap things, that doesn't surprise me. I think RAM is the key. It is for your opera, but not for Cameron's example, which LilyPond doesn't take more than 200 MB to compile. I've profiled the execution, but don't know what to conlude from this info; if anyone is interested in looking at it, it weighs 3 MB (161 KB LZMA compressed). John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Long compilation times
Cameron Horsburgh a écrit : I'm running a 2.4 GHz P4 with 1.25 Gig of Ram. The machine is aging, but it should be up to this challenge. I've noticed scores compile much quicker on much lower specced machines, so I'm suspecting something peculiar to my installation, but I don't know where to look. The exclusive use of spacer rests may be a bit perverse to process by LilyPond; is it faster if you replace all spacer rests s1 with full rests R1? I think this has little to do with your installation. Does anybody have any idea what could be wrong? Or is it normal to take 13 minutes to process a score with virtually no music? On my Intel 64 bit box, I get it to compile in 94 seconds: real1m33.675s user1m28.378s sys 0m0.721s This is much for such a simple score. Anyway, here's the file in question: ragged-last-bottom = t ragged-bottom = t What do you expect to get with these settings? John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: First Frog Task
Le dimanche 04 janvier 2009 à 20:05 -0700, Carl D. Sorensen a écrit : > Anybody have complaints about using "_idoc"? That's fine. > I don't need to check the translations, right? No... > As long as the english > docstrings appear we're good, right? Yes, unless you take over Translations meisters job :-) Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: First Frog Task
Le dimanche 04 janvier 2009 à 17:02 -0700, Carl D. Sorensen a écrit :
> I don't understand the significance of the change from _i to _idoc (which I
> would recommend instead of _doc). What is the difference between the
> "lilypond gettext domain" and the "lilypond-doc gettext domain".
The difference is about which domain each string is translated in:
po/{lilypond.pot,*.po} for domain lilypond, and
Documentation/{lilypond-doc.po,*.po} for domain. PO files are loaded,
installed and managed in radically different ways depending on the
domain: lilypond domain is to be installed and is loaded at each
lilypond execution, and it is managed by translation, whereas
lilypond-doc is not installed (it might be in the future), not loaded by
lilypond binary and managed directly on Git by translators and
maintainers.
> How would
> I know that things are working properly after I changed all the docstrings
> and the define-music-function macro?
Just compile the docs and check that music functions docstrings still
appear in the docs.
Cheers,
John
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: using Ramdisk
Le dimanche 04 janvier 2009 à 09:33 +0100, Thomas Fehr a écrit : > I'd like to use Lilypond in an interactive music learning program where > short response times are needed. I think running Lilypond on a ramdisk > could help. Does anyone know how to do that? I'm not sure a ramdisk will increase performance much, but it is surely much work. If you want short response times, use a machine with enough RAM, so that even if first invocation is a bit slow, further invocations will use disk cache in RAM. 512 MB of RAM is the bare minimum on a modern GNU/Linux with a fat desktop like Gnome or KDE, but several gigabytes are not too much if you run big or many ly files, or if you use a lot of programs simulatneously. HTH, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: using Ramdisk
Le dimanche 04 janvier 2009 à 23:23 +, Anthony W. Youngman a écrit : > WARNING! > > I think some things (notably source control) depend on atime so be > careful. I have used noatime for years without noticeable inconsistency with Git and CVS. Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Harmonic question
Le dimanche 04 janvier 2009 à 11:19 -0800, Graham Percival a écrit : > No; references is the correct place. If people skip over the > references to previous docs, then it's their own fault. We simply > /cannot/ add links to everything in all places in the docs; the > best we can do is have a consistent format/policy and stick to it. > Even if the policy doesn't make sense to everybody at first, if > it's used consistently they'll get accustomed to it. Thanks, my memory wasn't up to date with the policies, I'll reread them. Best, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Harmonic question
Le dimanche 04 janvier 2009 à 14:50 +, Trevor Daniels a écrit : > I've now added a ref to Harmonics in References for for fretted strings in > NR 2.4.1. I guess you mean 328df0d0d386fb553062680fd3c5be6d47548218 "Docs: NR 2.4 Fretted: Add ref to Harmonics" (tagged as 2.12.1-1)? > Do you think this is adequate? It certainly is, but I'm not sure people who read "Default tablatures" node will have the idea to find this link there. I was rather thinking of a link directly in running text and "See also". Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: First Frog Task
Hi Carl, Le vendredi 02 janvier 2009 à 20:16 -0700, Carl D. Sorensen a écrit : > I've attached a file README-contrib.txt, which is an attempt at what one of > you described as "Frogging for Dummies". It gives at least a brief > introduction to the key issues that I remember as obstacles when I got > started with LilyPond development. This is an excellent introduction! I only have one remark: the sentence "There is no one-page listing of the entire file tree, and there's no table of contents or index for the location of the various files." is misleading IMO: there are about 3000 source files, so any one-page listing of the entire file tree would not be very usable, and ROADMAP lists what you should expect to find in each directory. I suggest you replace the sentence above with something like "Any one-page listing of the entire file tree would not be very usable, as the tree contains about 3000 source files; however, " You could argue that most entries in ROADMAD could be elaborated with more explanations. > When you're done with this task, each function for which you are responsible > should have an internationalizable docstring. By internationalizable, I > mean that it will look like (_i "This is the docstring."), rather than "This > is the docstring." Because we are adding internationalizable docstrings, > you'll need to check even the functions that have docstrings. We'll probably have to replace _i with something like _doc to make sure the strings go to lilypond-doc gettext domain and not lilypond, but this can wait until the Frogs have completed documentation of all functions. Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Problem with site and documentation
Le vendredi 02 janvier 2009 à 21:15 +, Alberto Simões a écrit : > Erm, it is working now. I sure I tried it various times (firefox3). I cross fingers for you :-) > Could somebody else correct the issue meanwhile, or am I getting mad? We can't correct the error you may have encountered if you don't - try to reproduce the problem and explain us the steps you did exactly, - tell us the exact error message, - tell us about your exact OS and web browser version. Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Problem with site and documentation
Le vendredi 02 janvier 2009 à 20:34 +, Alberto Simões a écrit : > But when following the link to documentation > http://lilypond.org/web/documentation > it fails. What is your browser and which failure do you get exactly? What's the error message ? I can't reproduce any failure with this URL, it works for me. Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
[Fwd: Re: problem with hidden notes]
[private reply forwarded to list] --- Begin Message --- At 10:10 p.m. 30/12/2008, you wrote: Le mardi 30 décembre 2008 à 19:44 +0100, kristof a écrit : > as a suggestion for improvement of the manual: i must say that > 'Educational use' is not the first place where i would go looking for > something like this.. There must be a better name for this section, or subsections it contain could be moved elsewhere... it has already been discussed many times but no good solution has been found yet, so we welcome your concrete suggestions. personally i'd rather expect it under 'Contemporary Notation'.. or maybe a 'Special tricks' section under 'Advanced Notation'. guess people may want to hide notes for quite different reasons.. > is there somewhere a list of all predefined commands? http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Overview-of-available-music-functions thanks! apparently some functions are lacking here. i can't find hideNotes and unhideNotes for example.. cheers, Kristof --- End Message --- ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problem with hidden notes
Le mardi 30 décembre 2008 à 19:44 +0100, kristof a écrit : > as a suggestion for improvement of the manual: i must say that > 'Educational use' is not the first place where i would go looking for > something like this.. There must be a better name for this section, or subsections it contain could be moved elsewhere... it has already been discussed many times but no good solution has been found yet, so we welcome your concrete suggestions. > is there somewhere a list of all predefined commands? http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Overview-of-available-music-functions You could have found this in the Appendix under Identifiers. Few functions are documented, I'm adding documentation for more of them tonight. Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Dutch LilyPond user forum/mailing list?
Hi Wilbert, Le mardi 30 décembre 2008 à 21:13 +0100, Wilbert Berendsen a écrit : > every now and then somebody asks me: is there a Dutch user forum for LilyPond > users? As far as I know there isn't. > Maybe someone knows, or has a suggestion how to setup one. > > (Antwoorden mag ook in het Nederlands -:-) You might want to create a mailing list on lists.gnu.org (like this list, or LilyPond French-speaking list), or a Yahoo! or Google group, or a web forum. For example, if you'd like to set up a list on gnu.org, create an account on https://savannah.gnu.org/account/register.php then ask there for joining LilyPond (look it up in "Projects"), then submit a request for creating a mailing list. Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Diatonic/modal transposition function (John Mandereau)
Le lundi 29 décembre 2008 à 12:33 +0100, Tao Cumplido a écrit :
> As far as I understand it it works independent from a key signature so
> it doesn't matter if the key is in C or not.
>
> The function says taht you transpose a pattern in a given key for X
> steps, so in your example you transpose a pattern in a-minor one step
> up, and from C one step is D.
Correct.
> Would it be possible to make \diatonicTranspose recognize the key
> automatically?
Yes, if you know how to retrieve a context property -- I've started
looking at this, this is less trivial than setting context properties
with \set. It would not be named \diatonicTranspose, though, as this
function must keep a general enough purpose; would \keyDiatonicTranspose
be a sensible name?
> It would save a lot of typing.
> e.g.:
>
> motive = { c'8 d'8 }
>
> \new Staff
> {
>\key c \major
>\motive
>\diatonicTranspose #1 \motive
>\diatonicTranspose #2 \motive
> }
> Maybe the same for modeTranspose, that I only have to specify the mode
> I transpose into.
> This would be especially useful for minor keys because a motive is
> often transposed into minor melodic/harmonic.
Certainly. The problem is, it's not possible to retrieve the current
key signature as a context property at parsing stage, because contexts
(and thus context properties) are built in the next stage "music
interpretation". A dirty solution is defining a custom \key command
(e.g. defining \myKey that calls \key and stores the tonic and scale in
global variables), then reusing global variables in a
\keyDiaonicTranspose command; the downside of this is, it would be too
dirty for inclusion in LilyPond. A clean solution is delaying
evaluation of the diatonic applyContext; here's a sample based on
functions I sent in
http://lists.gnu.org/archive/html/lilypond-user/2008-12/msg00849.html
%%% Begin snippet %%%
#(define (lookup-context-property c symbol)
(if (ly:context? c)
(let ((v (ly:context-property c symbol)))
(if (and v (not (null? v)))
v
(lookup-context-property (ly:context-parent c) symbol)))
#f))
keyDiatonicTranspose =
#(define-music-function
(parser location pitch-note1 pitch-note2 music)
(ly:music? ly:music? ly:music?)
"Transpose music diatonicly by from pitch-note1 to pitch-note2
in scale on tonic-note."
(make-music 'ApplyContext
'origin location
'procedure (
lambda (c)
(let ((k (lookup-context-property c 'keySignature)))
(ly:interpret-music-expression
(make-music
'ContextSpeccedMusic
'property-operations
'()
'context-id
(ly:context-id c)
'context-type
(ly:context-name c)
'element
(mode-transpose
pitch-note1 pitch-note2 #{ c #} k #{ c #} k music))
(ly:context-find c 'Global))
minorPattern = {
c'2 ~ c'8 d'16 ees' f' g' aes' bes' c''4 g' ees' c'
}
{
\key c \minor
\repeat unfold 2 c'1
\keyDiatonicTranspose c d \minorPattern
}
%%% End snippet %%%
Note the strange spacing I get in the attached PNG; it even segfaults if
I add c'1 after "\keyDiatonicTranspose c d \minorPattern". I'll reduce
try to reduce the problem down and submit a bug report.
> I guess the best solution would be to have both options available,
> e.g. just to specify the key if necessary and automatic recognition of
> the current key if no key is specified.
It is hardly possible to have optional arguments in music functions,
because AFAIK the parser grabs next input tokens according to the music
function prototype. Having music functions with variable argument count
would make the parser horribly complex and would create ambiguous cases.
> Another thing I was thinking about is maybe using interval numbers
> instead of steps for the integer, so that #2 tranposes a second up and
> #-4 a fourth down etc.
This would make the arithmetic more complicated (as it already does to
people that learn western music theory :-P), a better solution is to use
interval names as I suggested to Stefan, or even better replace this
integer argument start pitch and final pitch as I proposed.
> It's definitely an awesome function and it makes constructing a piece
> with motives possible.
Yeah, as my flatmate says this function is relevant to composition and
not pure music typesetting, but by design LilyPond already offers input
facilities with this kind of side-effect (or at least it has this
power).
Best,
John
<>___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Harmonic question
Le lundi 29 décembre 2008 à 22:53 +, Trevor Daniels a écrit : > Yes. The warning under Harmonics in 2.3.1 in the Notation Reference says: > > "Note: Harmonics must be defined inside a chord construct even if there is > only a single note." Should we add copy this warning into "Common notation for fretted strings" or add there a "See also" reference to 2.3.1? I know about the "no duplicate information" rule but I feel like a "See also" might not be enough. John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Diatonic/modal transposition function (John Mandereau)
-pitch->modal-pitch
(lookup-music-property pitch-note1 'pitch)
scale1
tonic-diff1
(music-map
(lambda (event)
(let ((p (ly:music-property event 'pitch)))
(if (ly:pitch? p)
(ly:music-set-property!
event
'pitch
(modal-pitch->ly-pitch
(degree-transpose
(ly-pitch->modal-pitch p scale1 tonic-diff1)
modal-pitch-delta
7)
scale2
tonic-diff2)))
event))
music)))
modeTranspose =
#(define-music-function
(parser location pitch-note1 pitch-note2 tonic-note1 scale1 tonic-note2
scale2 music)
(ly:music? ly:music? ly:music? list? ly:music? list? ly:music?)
"Transpose music diatonicly by the interval between pitch-note1
and pitch-note2, interpreting pitches in scale1 on tonic-note1
and producing pitches in scale2 on tonic-note2."
(mode-transpose
pitch-note1 pitch-note2 tonic-note1 scale1 tonic-note2 scale2 music))
diatonicTranspose =
#(define-music-function
(parser location pitch-note1 pitch-note2 tonic-note scale music)
(ly:music? ly:music? ly:music? list? ly:music?)
"Transpose music diatonicly by from pitch-note1 to pitch-note2
in scale on tonic-note."
(mode-transpose
pitch-note1 pitch-note2 tonic-note scale tonic-note scale music))
pattern = \relative c' { c2~ c8 d16 e f g a b c4 g e c }
\new Staff {
\pattern
\diatonicTranspose c d c \major \pattern % I -> II
\diatonicTranspose c e c \major \pattern % I -> III
}
% mixing lydian and mixolydian modes
milydian = #`(
(0 . 0)
(1 . 0)
(2 . 0)
(3 . ,SHARP)
(4 . 0)
(5 . 0)
(6 . ,FLAT))
melodie = \relative c' { \times 2/3 { cis8 d e } f2 }
\new Staff {
\time 3/4
\melodie
\modeTranspose cis d g \milydian d \lydian \melodie
\modeTranspose cis dis' g \milydian e \lydian \melodie
}
--
John Mandereau
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Diatonic/modal transposition function
Le lundi 29 décembre 2008 à 15:44 +0100, Hans Aberg a écrit : > Is this synced with the work by Graham Breed, who has worked on > microtonal extensions? - See the developers list. I assume you refer to "Mictrotonal support" thread, which is kind-of a follow-up of "Diatonic notation system" (traffic on -devel is so high these days). This work is not synced at all with Graham's work, but it tries not to naively assume any temperament; in current state it only works with 7-notes scales, but the arithmetics on alteration works with any kind alteration, semi-tones or microtonal alterations. BTW I'm sure it is feasible to extend these transposition functions to scales with other lengths assuming equal semi-tones temperament (E12) (e.g. for Messiaen's modes), but I'm not knowledgeable enough about scales and modes definitions you discussed with Graham on -devel to tell how the functions I wrote should be extended to support these scales. Best, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Diatonic/modal transposition function
nspose music from scale1 on tonic pitch-note1
by degree-delta to scale2 on tonic pitch-note2."
(mode-transpose
pitch-note1 scale1 degree-delta pitch-note2 scale2 music))
diatonicTranspose =
#(define-music-function
(parser location pitch-note scale degree-delta music)
(ly:music? list? number? ly:music?)
"Transpose music by degree-delta in scale on tonic pitch-note."
(mode-transpose
pitch-note scale degree-delta pitch-note scale music))
pattern = \relative c' { c2~ c8 d16 e f g a b c4 g e c }
\transpose c g \new Staff {
\pattern
\diatonicTranspose c \major #1 \pattern % I -> II
\diatonicTranspose c \major #2 \pattern % I -> III
}
% mix between lydian and mixolydian
milydian = #`(
(0 . 0)
(1 . 0)
(2 . 0)
(3 . ,SHARP)
(4 . 0)
(5 . 0)
(6 . ,FLAT))
melodie = \relative c' { \times 2/3 { cis8 d e } f2 }
\new Staff {
\time 3/4
\melodie
\modeTranspose g \milydian #-3 d' \lydian \melodie % IV -> I
\modeTranspose g \milydian #3 e' \lydian \melodie % IV -> VII
}
--
John Mandereau
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: no download
Le dimanche 28 décembre 2008 à 17:36 +, Ignacio a écrit : > Hello, > I am trying to download versio 2.12 for MacOS Intel, but the link cannot > find the server. This is fixed now -- not by me, thanks to the webmaster. Best, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Convert-ly in 2.12
Le dimanche 28 décembre 2008 à 21:48 +1100, Nick Payne a écrit : > After installing 2.12 (running on Windows Vista), I notice that when I run > convert-ly against an old ly file, it changes the version in the file to > 2.11.66: > 2.11.66 > > Seeing that this is supposed to be the stable version, I think it > should put the current version number in the file, and not the last > development version after which there were no conversion changes > needed. Sorry, conversion changes after last development version (2.11.65) are really needed, but they were wrongly named for 2.11.66. This will be fixed in release 2.12.1. Thanks for the report -- John Mandereau ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond v12 download links
Le dimanche 28 décembre 2008 à 09:33 +0100, Francisco Vila a écrit : > 2008/12/28 Bill Mooney : > > Greetings, > > The links on the LP site for downloading the latest version seem to be > > incorrect... ?!? > > Can anyone clarify / correct this? > > I reported this to the -devel list yesterday. Use this link in the meantime: > > http://lilypond.org/download/binaries/ Please use http://download.linuxaudio.org/lilypond/binaries/ instead Best, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: question about transposing an interval of a 4th
Le lundi 22 décembre 2008 à 15:14 +0100, James E. Bailey a écrit : > Am 22.12.2008 um 14:04 schrieb John Mandereau: > > Indeed: there is currently no thing in all LilyPond documentation that > > introduces Scheme programming for non-programmers. > And there shouldn't be, in my opinion. Why not? I'm sure a not so small amount of users would like to program with LilyPond, so revising and extending the Scheme tutorial is a solution IMHO. > > We can't share this on this list, but it'd be cool to have an > > introduction to programming based on Scheme and demonstrating > > applications in LilyPond; however, even this is a lot of work and > > there > > are more urgent and basic things to do in the next 2 months. > > Given that, I'd say that the easiest solution would be to just tell us. It's not just a matter of telling you; teaching how to fish (or programming Scheme) takes a long time, and I don't have that much time to teach Scheme on the list for free. GF proposed a lot of links in this thread, I'm sure you'll find something that will fit your needs. > Incidentally, he did make it clear, he wants a diatonic fourth. So, c > sharp in trumpet one is g natural in trumpet 2, not g sharp. Then wait for the diatonicTranspose function until Christmas :-P John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: question about transposing an interval of a 4th
Le lundi 22 décembre 2008 à 10:56 +0100, James E. Bailey a écrit : > Am 22.12.2008 um 03:52 schrieb Graham Percival: > Oh, I've read the Learning Manual cover to cover (well, it may have > been changed since then, it was some months ago), and I don't > understand Scheme. Indeed: there is currently no thing in all LilyPond documentation that introduces Scheme programming for non-programmers. > > Give a man a fish, teach a man to fish... > Apparently you, valentin, nicolas and John are the only people on this > list who know how to fish. And no one's sharing how. We can't share this on this list, but it'd be cool to have an introduction to programming based on Scheme and demonstrating applications in LilyPond; however, even this is a lot of work and there are more urgent and basic things to do in the next 2 months. Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: question about transposing an interval of a 4th
Le dimanche 21 décembre 2008 à 09:47 -0800, Graham Percival a écrit :
> On Sun, Dec 21, 2008 at 11:26:16PM +1100, Cameron Horsburgh wrote:
> > He wants it diatonic, so it's not that easy. \transpose c' g {a b c}
> > would produce {e fis g} instead of {e f g}.
>
> Oops, I forgot my first-year theory. In this case, he'd need to
> write a scheme function. Actually, it wouldn't be hard at all...
> this is a perfect intro-level scheme tweak.
>
> I leave it as an exercise for the reader. Neil, Trevor, Valentin:
> please don't give the answer. :)
Ha! I won't give the whole answer either, but as I already analyzed the
problem some time ago, I can't resist telling about it here, only
figuring out data types and Lily Scheme function to be used (see Scheme
functions in the Internals Reference) and the actual Scheme code writing
are left now.
ly/scale-definitions-init.ly provide a few scale definitions; each scale
definition maps a scale degree to a pitch difference (measured in whole
tones) against the diatonic scale.
Then, diatonic transposition from (scale1 pitch1 degree1) to (scale2
pitch2 degree2) (where pitchx carries both the octave and the tonic) is
a matter of composing three functions:
- converting each pitch from LilyPond representation (octave note alter)
to (octave scale-degree alter) representation using the inverse map of
scale1;
- mapping (octave scale-degree alter) to
((octave + virtual-new-degree/7) (virtual-new-degree mod 7) alter)
where virtual-new-degree = scale-degree + degree2 - degree1
- converting (new-octave new-degree alter) back to a Lily pitch using
scale2.
Transposition in modes with more than 7 notes is also possible but it's
quite harder, unless we use more than 7 note names :-P.
Well, diatonic transposition should definitely be a builtin function.
If nobody has written it in a few days, I'll take it over.
Cheers,
John
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: passage à lilypond depuis pmx
This is an English-speaking only list, please send your messages in French to [EMAIL PROTECTED] as mentioned on http://lilypond.org/web/about/index.fr.html Here's a quick and partial translation of your message in case somebody has an answer to your question on this list. """ Hello, I'd like to convert my scores in PMX or MusixTeX format to LilyPond; do you know about some converter which could at least convert individual voices of the score? I've already looked for this with a web search engine, but all references I found were empty, the mentioned pieces of sofware are no longer available. """ Le jeudi 20 novembre 2008 à 19:13 +, Richard Fournier a écrit : > Bonjour, > > Je programme actuellement en pmx (ou en musixtex) et je suis tenté par le > passage à lilypond. Mais j'aimerais pouvoir convertir mes fichiers pmx dans le > format lilypond. Si tout n'est pas parfait ce n'est pas grave, mais j'ai au > moins besoin de récupérer chacune des voix. > > Existe-t'il une solution ? > > J'ai exploré le net avant de vous contacter, mais rien de ce que j'ai trouvé > n'était encore disponible. Il y a manifestement eu une période pendant > laquelle > la conversion était possible, mais je ne trouve pas les anciens outils > mentionnés. > > Si vous avez quelques éléments de solution, je vous serez très reconnaissant. > Merci d'avance. > Cordialement, > Richard Fournier -- John Mandereau <[EMAIL PROTECTED]> ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
RE: pdf file
On 2008/11/14 16:40 -0500, Slattery, Tim - BLS wrote: > > It's useful if you want both PDF and any other output format > > besides PostScript. Ah sorry, I meant any *printed* output format besides PostScript. > So if I have language in my *.ly file specifying MIDI output and I want > a PDF too I have to use the --pdf flag? No, you don't, which you can certainly verify it yourself. Best, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: pdf file
On 2008/11/14 16:10 -0500, Tim Slattery wrote: > "Francisco Vila" <[EMAIL PROTECTED]> wrote: > >Output is PDF by default. > > Then what does the flag do? It's useful if you want both PDF and any other output format besides PostScript. Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: how lilypond-book deals with multiple LP releases on disk
On 2008 22:08 -0800, Mark Polesky wrote: > I'm finally trying lilypond-book (on Windows XP), > coming up against some frustrations. For some reason, > the documentation has left me confused, but I > think I'm figuring stuff out anyway. Problem is, I > currently have both LilyPond 2.10.33 AND LilyPond > 2.11.63 on my system, and when I run lilypond-book, > it automatically runs 2.10.33, and I want it to run > 2.11.63 without having to uninstall 2.10.33. > > Any suggestions? Besides Trevor's suggestion, which has been more tested, you might want to try --process command line option, or make sure LilyPond 2.11.63 directory comes before 2.10.33 directory in your PATH. Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: WANTED: Design for documentation (Photoshop power users!)
On 2008/10/26 01:41 +0200, Robin Bannister wrote: > Reinhold Kainhofer wrote: > > How about "Overview" instead of "Index"? > > A better choice! > And I counter with "Documentation Home". > > But a second word is overkill. I'd like "Up to" proposed by Francisco, and "documentation home" is unambiguous IMHO, so I propose "Up to documentation index" (with capitalization if it's appropriate). Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: WANTED: Design for documentation (Photoshop power users!)
Le samedi 04 octobre 2008 à 22:18 +0200, Reinhold Kainhofer a écrit : > Am Samstag, 4. Oktober 2008 schrieb Robin Bannister: > > Without the prefix the title is then just e.g. "Learning Manual", which > > corresponds to what you see in the documentation overview. > > Yes, but that was the only string (the title of the @top node), that is > accessible from texinfo... I don't want to hardcode the manual names (and > their translations!!!) into the .init script, which is -- although tailored > to our ideas for our documentation -- very general and can be used with any > other texinfo file just as well and make that look like our documentation. Maybe a compromise would be to add a hack in the .init file, which would remove "GNU LilyPond - " in the TOC title. > Okay, so basically, you want (just like anyone of use) a link to the back to > the documentation index... I've already said that we just need a good idea > where to put it. The design needs to be fit to that, of course, but I have > trust in the designers that they'll manage this just as well ;-) > So, I'm all up for good ideas how such a link should look and where exactly > it > should be placed. This is probably a too simple idea, but what about adding "[Documentation home]" at beginning of the navigation bar [Top][Contents][Index][ ? ] ? Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Does lilypond takes advantage of multi-cores on windows?
On 2008/10/03 18:42 -0700, sdfgsdhdshd wrote: > Han-Wen Nienhuys-5 wrote: > > One tricky aspect is that the GUILE evaluator is fundamentally broken: > > it rewrites Scheme expressions for memoization in thread-unsafe ways > > all over the place. > > > > For Lily itself, I think it will also be very tricky: evaluating grob > > properties through callbacks is assumes that there is only one > > evaluation going on at the same time. > > > > You mean there must be only one .ly file on the command-line? No, we were talking about the possibility of parallelizing code to take advantage of multi-core CPUs to process _one_ file at the same time, but you can of course take advantage of a multicore CPU if you process several ly files at the same time with lilypond -djob-count=NUMBER LY_FILES -- John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Does lilypond takes advantage of multi-cores on windows?
On 2008/10/03 11:14 -0700, sdfgsdhdshd wrote: > Anthony Boyd-2 wrote: > >> -djob-count=[number of cores] > > > > I don't think that job count changes things when you process a single > > input file though. If you specify multiple input files to process > > then lilypond will fork off into different jobs to get the work done. > > > > Are the new processes only on one processor? or several? It's up to the operating system kernel to spread the load on all CPUs (or CPU cores); e.g. if you run "lilypond -djob-count=2" and you have no other processor time-consuming tasks at the same time (if this can ever happen on Vista :-P) on a dual core CPU, the kernel should spread each lilypond process on one different core. The reality may be a bit more complex, but this is roughly the principle. It may be possible to parallelize some portions of LilyPond code to take advantage of multi-core machines, which gradually become quite common, I'm tempted to have a look at it in the next months, but don't hold your breath :-) Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: WANTED: Design for documentation (Photoshop power users!)
On 2008/09/30 14:04 -0700, Patrick Horgan wrote: > Well done:) I still prefer Patrick's style and wish it were the > default. +1 John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: WANTED: Design for documentation (Photoshop power users!)
On 2008/09/17, Reinhold Jainhofer wrote: > On Sunday 14 September 2008 21:50:36 Patrick McCarty wrote: > > I agree that the language selection should be included in the footer, > > but I'm not sure how the buildscript will have to be modified. I'm not sure how to move the lanugage menu into the footer: if we do this, it should be as visible as before, e.g. with normal text size (i.e. bigger than the rest of the footer), or with different colors. As soon as we agree on a formatting sample, I'll modify the buildscript accordingly. > Currently, the footer looks bad with Patrick's design on the server, > because I have not changed the footer to the HTML structure suggested by > Patrick. > Is everyone okay to change the footer lines to the following? > This page is for LilyPond-2.11.59 (development-branch). > Your suggestions for the documentation are welcome, please report errors > to our bug list. I approve this. I guess you may use usual Graham's ultimatum formula "Unless anybody complains" in such cases. IMHO I prefer Patrick's design over Andrew, it's more colorful but still serious enough (as Valentin already wrote), and I second Patrick Horgan comment on links color: maybe we could make links a bit more blue? We might manage to merge both style sheets into one, but let's hurry up if we want this to make it into 2.12.0 ;-) Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: another emacs osx question
Le lundi 22 septembre 2008 à 00:21 +0200, James E. Bailey a écrit : > This was actually a late reply to the first time I posted this question (in > august). It was solved about a month later. > http://lists.gnu.org/archive/html/lilypond-user/2008-09/msg00301.html Oops, sorry for the confusion, I overlooked (and wrongly rewrote in English) the date (mmh, maybe I should run my email client in English :-P). Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: another emacs osx question
On 2008/09/18 13:33 +0200, James E. Bailey wrote: > Now that emacs can actually run lilypond, I have another problem, I > can't run a command on the master file: it doesn't escape the spaces > in filenames or folder names. Is there any way I can change this? I don't understand; haven't this problem already been fixed (the fix in Emacs mode made it through 2.11.59)? If it hasn't, please specify which file name with full path you tried, and which exact commands you issued in Emacs with the keyboard and/or menu entries. Best, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: emacs-mode
On 2008/09/12 10:15 +0200, James E. Bailey wrote: > Well, now that lilypond can compile a file in emacs, I've been looking > around, getting myself acquainted with the various options. > Apparently, the 2tex option calls lilypond as lilypond -b tex > filename.ly The version of lilypond that I have installed says that > should be -f tex (assuming I'm using the tex backend in my file). > Also, just calling lilypond with the tex backend reported this: > Layout nach »Litany.tex« ausgeben.../Users/jamesebailey/share/lilypond/ > 2.11.58/scm/framework-tex.scm:197:26: While evaluating arguments to > last-pair in expression (last-pair pages): > /Users/jamesebailey/share/lilypond/2.11.58/scm/framework-tex.scm: > 197:26: Unbound variable: pages The TeX backend is no longer supported, it has been replaced by the PostScript backend between 2.4 and 2.6 releases, so I removed menu commands and keyboard shortcuts related to TeX and DVI in Emacs mode; the menu command "2Midi" is broken (it calls view PS), I'll junk it of fix it later. Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: WANTED: Design for documentation (Photoshop power users!)
Le vendredi 12 septembre 2008 à 17:32 -0600, Andrew Hawryluk a écrit : > > Andrew, feel free to suggest a new color for the footer :-) > > > > Cheers, > > John > > You could change the footer from #e8ffe8 to #e7efe3 and the border > from #c0ffc0 to #ccd3cc. Thanks, I applied these changes. > It looks like the padding/spacing in the > footer could be improved I second this; you could send us a CSS fix for this if your like. > but for now I'm more curious to see Patrick's > design (and others). So am I; I applied your stylesheet because I thought it's a significant improvement in contrast with the previous one; further submissions may not be pushed to Git master branch until we have reached a consensus, instead we could show new style sample pages on a web site. Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: WANTED: Design for documentation (Photoshop power users!)
On 2008/09/13 01:36 +0200, Reinhold Kainhofer wrote:
> #rgb is the official CSS color shortcut for #rrggbb, see
> http://www.w3.org/TR/CSS2/syndata.html#color-units
Ah, I'll be less ignorant when I go to bed tonight, as we say in French :-)
> And yet, a font specification sneaked into the .css file:
>
> +h1.header {
> + font-weight: bold;
> + font-family: avantgarde, sans-serif;
> + font-size: 220%;
> +}
Junk avantgarde if you like (I don't know this font), but I see no
reason not to keep the big title in sans-serif; I think this is OK for
one unique title.
Cheers,
John
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: WANTED: Design for documentation (Photoshop power users!)
Le mercredi 10 septembre 2008 à 11:49 +0200, Reinhold Kainhofer a
écrit :
> Am Samstag, 6. September 2008 schrieb Andrew Hawryluk:
> > Here's my initial design submission for the docs - it's just a gentle
> > modification of the CSS file:
Cool! I applied it, and made some changes, see
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=b2d91785b770533fd27763c5b773855f6723fd98#patch3
BTW I don't know what "#CCF" was supposed to mean as a color.
> > - use "Century Schoolbook L" if available to match the LilyPond output
> > (Georgia is also a good option)
>
> Actually, on -devel we discussed fonts a while ago and decided not to put any
> font family in the .css file. The reason is that each user has different
> preferences and different fonts he is used to for viewing web pages. Any
> other font will only be confusing / make the output look unusual.
> In particular, I like a sans-serif font for viewing web pages, because I
> think
> that makes it much easier to read on screen (the is no additional clutter
> coming from the serifs, that the eye must comprehend, so there is less
> distraction from the main contours of the glyphs), while e.g. John or Graham
> prefer a serif font. We have all configured our browser to show the sans /
> serif fonts as default fonts, so LilyPond's documentation should honor that
> setting, too.
I second this.
>> - the colors are taken from the Monet "Waterlilies" on the LilyPond
homepage
I find it a good idea, even if we might decide to change this image:
it's a small heavily compressed JPEG image, this is not appealing
enough, LilyPond deserves better graphics on its start page. Feel free
to propose a replacement for it, e.g. a graphical mixture of Monet
Waterlilies and some LilyPond output...
> > I didn't change the color of the box at the bottom ("This page is for
> > LilyPond-2.11.58") because it was styled right in the HTML file.
>
> Oops, yeah, that should be moved to the CSS, too.
Done in Git. BTW I made html_postprocessing.py apply this style sheet
to toplevel pages too: the documentation index, the examples page,
translation status pages and developers page.
Andrew, feel free to suggest a new color for the footer :-)
Cheers,
John
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: emacs question
On 2008/09/10 16:53 +0200, Reinhold Kainhofer wrote: > > I'd rather fix the bug completely before speaking up, but this thread is > > inflating a lot: in elisp/lilypond-mode.el line 647 (in function > > LilyPond-command-expand), file should be quoted and escaped. > > Ahm, no line 647 is fine (just passes on the file variable to the next > recursion). The real culprit is in line 636 (split-file-name file), where > file should be escaped. Oops, you're right. > Alternatively, the dir and base variables can be > escaped after splitting... Yep, that's what I did in the patch. Thanks for the hint! Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: emacs question [FIXED]
On 2008/09/10 16:41 +0200, James E. Bailey wrote: > 6) I think somewhere, the quotes are being stripped. Probably, but escaping the spaces instead of quoting the whole file name also works with (ba)sh, and shell-quote-argument Emacs function does it well (see below). > On other platforms using emacs, does the output look similar? Yep, it does on my GNU/Linux. The following fix works for me, I'm pushing it to Git, it will appear in release 2.11.58 or .59 diff --git a/elisp/lilypond-mode.el b/elisp/lilypond-mode.el index 769331f..80a3f29 100644 --- a/elisp/lilypond-mode.el +++ b/elisp/lilypond-mode.el @@ -638,8 +638,7 @@ Must be the car of an entry in `LilyPond-command-alist'." (base (cadr l))) (LilyPond-command-expand (concat (substring string 0 b) - dir - base + (shell-quote-argument (concat dir base)) (let ((entry (assoc (substring string b e) LilyPond-expand-alist))) (if entry (cdr entry) "")) > Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LSR cannot be found.
On 2008/09/10 14:32 +, Josef SCHLUESSEL wrote: > Neither SAFARI nor FIREFOX can find lsr.dsi.unimi.it/ > (Maybe half a year ago there was absolutely no problem with LSR.) > What can I do? Wait until LSR is up again (in two weeks or later). Search the list archives for more information. John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: emacs question
On 2008/09/10 15:11 +0200, James E. Bailey wrote: > I just wish someone with a little elisp help could point me toward the > part of whichever file determines how the file is processed in emacs > so I could learn enough to be able to add " " to it. I'd rather fix the bug completely before speaking up, but this thread is inflating a lot: in elisp/lilypond-mode.el line 647 (in function LilyPond-command-expand), file should be quoted and escaped. The only detail I haven't looked at yet is, does Emacs provides a function for escaping a file name for use in a shell command? (I know nothing about Emacs list and Emacs standard library). Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: convert-ly broken on Mac OS X "Tiger"?
On 2008/09/09 21:31 -0700, Kurt Kroon wrote: > I'm getting an error when I try to update a file to v.2.11.57 on Mac OS X > "Tiger", running on a G4 PowerBook. (The file works fine in v.2.10.33, > though I need to do some more tweaks to fix some minor layout issues.) > Has anyone else encountered this problem? > Has anyone who has encountered it found a way to resolve it? (even as far as > hacking convertrules.py) This is a known issue: Python scripts provided with LilyPond officially require Python 2.4 or newer, but MacOS X Tiger only provides 2.3. In this case, convert-ly conversion rules have been rewritten using decorator syntax rules during 2.11 development, which Python 2.3 doesn't support. Providing Python 2.4 in GUB binaries for MacOS X Tiger is probably the right solution, but it's not too hard to do only if Python 2.4 can be cross-compiled on Linux for MacOS X. Not I'm not able to do this in GUB (yet). In the meantime, you may want to install Python 2.4 or 2.5 on your system. Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: --evaluate command line option
On 2008/09/10 10:32 +0200, Johan Vromans wrote: > The first thing I can find is dated Sun, 24 Sep 2006 11:36:08 -0700, > where you replied: "This has been discussed on either this mailing > list or the -devel list, I think between 6 and 12 months ago, but I > forget what the answer was." > > Then there's a posting from Han-Wen dated Wed, 4 Feb 2004 17:21:38 > +0100, that hints at the possibility. > > Any other suggestions? lilypond --help --evaluate is supported by Lily 2.11, but I don't remember for 2.10. HTH, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: different tempi
On 2008/09/09 19:57 +0200, Reinhold Kainhofer wrote: > Well, as one of my teachers at school used to say: "Believing means not > knowing..." Attached is a simple lilypond file, which does exactly what you > want (modulo the 5/4 in the Vla staff, since that measure actually contains > 6/4 ;-) ). The trick is in removing the spanned bars from the StaffGroup and > insert an InnerStaffGroup for the staves before the Vla and one for the > staves after the Vla. For these InnerStaffGroups you can enable spanned > barlines to produce the desired result. Wow, you made the effort of typesetting the whole example, but adding and removing the same engravers in each InnerStaffGroup is not very clean, doing this in \layout is more appropriate. > PS: Now and again, I'm really astonished and fascinated about the power and > flexibility that LilyPond's Engraver and Context hierarchy brings! So I am! John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: different tempi
On 2008/09/09 12:45 -0400, Kieren MacMillan wrote:
> Werner LEMBERG wrote:
> > Currently, I believe that my problem can't be solved with the current
> > means of lilypond, and some extra coding is necessary.
>
> What about using InnerStaffGroup(s)?
Indeed (but I'm very puzzled the order of \consist-ed engravers is
important):
\score {
\new StaffGroup <<
\new InnerStaffGroup <<
\new Staff { c'1 c' c'4 }
\new Staff { \clef bass d4 e f g a1 a4 }
>>
\new InnerStaffGroup <<
\new Staff \relative c' { \time 3/4 f8 e f g a4 g2.~ g4 f8 e f4 }
>>
\new InnerStaffGroup <<
\new Staff \relative c'' { a2 d, e c c4 }
>>
>>
\layout {
\context {
\Score
\remove Default_bar_line_engraver
\remove Time_signature_engraver
\remove Timing_translator
}
\context {
\StaffGroup
\remove Span_bar_engraver
}
\context {
\InnerStaffGroup
\remove System_start_delimiter_engraver
}
\context {
\Staff
% the order of engravers matters here: e.g. if Timing_translator
% comes after Default_bar_line_engraver, barlines are messed up.
\consists Timing_translator
\consists Default_bar_line_engraver
\consists Time_signature_engraver
}
}
}
If LSR was up, I'd add there too; maybe we can add it to input/new if
it's worthwhile.
HTH,
John
<>___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond-latex
On 2008/09/01 18:19 -0400, Kieren MacMillan wrote: > > /usr/bin/python --version > > You'll see 2.3.5. > > ... or at least, Kieren would see 2.3.5, because of the error > > involving "set". I get it too, and have to edit lilypond-book > > manually whenever I get a new lilypond. > > Okay, manually editing lilypond-book to use the correct python > installation did the trick… Would using "#!/usr/bin/env python" at top of LilyPond Python scripts help solve this issue? Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: indexing
On 2008/08/26 22:13 +0100, Trevor Daniels wrote: > No one is working on the LM at the moment, Yes I am: I've finished the work on makefiles I had planned, so I'm going back to proofreading the Learning Manual (I'm at Chap. 4 "Tweaking output). > Are you able to obtain these source files from Savannah? How do you submit > your changes? You could simply mail any changed file back to me if you > like. Ralph, could you send both Trevor and me changed files? It'll be easier for everyone if I commit your changes, as I'm working on the same files. Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: (ot) Computer-assisted musical instrument tutoring: thesis complete
On 2008/08/23 09:30 -0700, Kurt Kroon wrote: > On 2008/08/23 12:13 AM, "Graham Percival" <[EMAIL PROTECTED]> wrote: > > > My thesis defense went very well, I've finished all > > corrections, and have submitted all the paperwork. Congratulations! Are you going on with a PhD? > > I'll be fixing the website and removing the GDP stuff the week > > after next, once I'm back from ICMC 2008. > > Should we retain an archive of what's there for the documentation team? I think so, but if Graham agrees, we should move this to a new namespace on http://lilypondwiki.tuxfamily.org and give credit to Graham in articles like "Documentation is a process, not a product". Using a wiki seems very important to me, because nobody currently leads the doc team any more, and it will save time for the future docs leader anyway. If we go this way, I'll give wiki accounts to all doc writers. Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: it's all up to you users (was: Please forget LM MG NR IR SL AU)
2008/8/18 Graham Percival <[EMAIL PROTECTED]>: > On Sat, 16 Aug 2008 18:42:38 +0200 > "John Mandereau" <[EMAIL PROTECTED]> wrote: >> Why not doing both? > > Because it's impossible to do both at the same time. It takes > time and energy to answer emails or write docs. > > That seems trivial -- surely everybody knows this already -- so > let's discuss a specific example. Don't spend too much time beating a dead horse... be it me or Valentin. In this case, I don't mean writing long and polite emails when handling related doc additions, but writing concise replies to let users know we're doing something to address some problem or lack in the docs, and if necessary having some discussion to make details clearer. > There's also some trickle down effects to consider. I've told > some doc helpers *not* to get involved with programming (or at > least to restrict their efforts in this direction) so that we > retain an actual "doc team". If we have 6 people working on the > docs, they can share the load, comment on each other's work, and > generally bolster each other's morale. If we only had 2 or 3 > people working on the docs, the strain on each person becomes much > larger. You have a very good point here. Maybe I'm going to dissappoint you (or maybe did I so a while ago? :-P), but I'm not going to spend a lot of time writing docs, although I'm interested a lot in proofreading. I'm starting a Master in IT, acoustics and signal processing applied to music, so it's vital I start hacking Lily in the coming months; I may want to start with new features easy to add like useful music functions, fingering diagrams for woodwinds... > I'm not saying this because I don't care about new users -- after > all, the whole *point* of documentation is to help users -- but > rather because I know that Valentin's concerned about the general > well-being of the project. And I'm concerned about Valentin > spending so much effort. I'm concerned about your effort in so long emails, although I'm going to miss their "inimitable" style :-). If you can't convince me in 5 to 15 lines, then a longer email won't do it better. Mathematicians, and math students like me concise and clear proofs -- you're clear but not always concise. > I'm infamous within my research group for being a "no-man". In > English slang, a "yes-man" is somebody who always agrees with his > boss. FWIW the French term for this is "béni oui-oui" :-) > Is this lilypond-user-fr? It looks like a very low-traffic list. It usually is, but it sometimes balloons up to ten emails a day, for 3 or 4 days. Best, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Absolute vs. relative pitches
2008/8/14 Trevor Daniels <[EMAIL PROTECTED]>: >> I wouldn't mind adding a section to LM 3 about absolute mode, with >> usage cases and whatnot. But I still really think that everything >> else in the docs should be \relative. > > Great! We are agreed, then :) I have even suggest to discuss it later, in Learning Manual 5 "Working on LilyPond projects": I think this is not as important as topics discussed in Chapter 3. I generally appreciate the progressive introduction of concepts in the Learning Manual (even if some details still have to be refined), which addresses the issue of the steep learning curve of LilyPond. Anyway we don't have time to deal with absolute vs. relative before 2.12.0... Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Second review of NR 2.7 Chords
2008/8/16 Neil Puttock <[EMAIL PROTECTED]>: > In selected snippets, chord-name-exceptions.ly and > chord-name-major7.ly aren't displayed properly (no title, lacking > %begin verbatim so the texidoc and version are visible) since there > are snippets with these names present in input/regression; they take > precedence over the LSR versions. Fixed in Git master -- this will be for .57 release. Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: it's all up to you users (was: Please forget LM MG NR IR SL AU)
2008/8/13 Graham Percival <[EMAIL PROTECTED]>: >It's a waste because, 7 days from now, there will be precisely > half a dozen people who are updating the documentation. There's > at least 50 people who can answer simple questions here. To be > efficient, those six people should spend their time updating the > docs -- better docs help everybody in the future, whereas writing > a detailed and polite email only helps one or two people right > now. Why not doing both? I find it normal that doc writers answer non-trivial questions and by the way digest the answers into our docs. This should be a part of the normal docs workflow: sollicitating users for proofreading rewritten docs is certainly a good thing, but on the opposite direction, interesting questions and comments from users can raise issues doc writers wouldn't have thought of by themselves. >(no, nobody will read the messages in the archives. That's > pure wishful thinking) Nobody... except doc writers, developers, advanced users, and I'm quite sure this will not change, because it's difficult to search the archives when you don't know the right keywords to use. > And who really cares how busy the programmers and doc > writers are? I mean, that's the whole point of open source, > right? The users get free software, documentation, and email > support. > Exactly, but users don't get all the features and support they want for free. Some features nobody wants to add for free, or dedicated user support might be sponsored. > As I said, I've tried polite recruitment. Take a look at the email > archives; probably about six, twelve, and eighteen months ago. It > seems to have worked for doc writers, but it hasn't worked for finding > (and keeping) -user support people. > On the French list, we never had to recruit people to provide support, users who recently discovered LilyPond help each other, developers and advanced users reply only if necessary (I expect somebody is going to shoot me for all unreplied messages there :-p). It seems this works on this list too, except that you feel concerned that developers and advanced users reply to so-called simple questions: IMHO it's up to everyone to judge how (s)he wants to spend its time. FWIW I'm too busy to read all emails on this list, but I follow a rule to try to be efficient: when I read an email on this list (or bug-lilypond) and nobody else has sent an appropriate reply, I reply in one of the following cases: a) I can write the reply in 2 minutes because I know the topic well, b) if I can fix a bug or improve the docs myself, I investigate and also take time to write a well-written reply. Everyone certainly has his (maybe implicit) own rules to decide how to spend time on the lists. > I know that at least two people are going to be offended by this email, > but I don't care -- if it results in just ONE person "taking ownership" > of being a polite -user email responder and making an honest effort at > replying to everything they can -- just **ONE** person who isn't already > part of GDP -- then I'll accept any amount of hard feelings the rest of > you throw my way. > The only feeling I'd like to finally throw your way is: have a rest and some vacation after your thesis conference! You certainly deserve and need it. I can't imagine how you could manage a huge emails load for so long time. Best, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Please forget LM MG NR IR SL AU
2008/8/11 Bertalan Fodor (LilyPondTool) <[EMAIL PROTECTED]>: > My point is that lilypond-user reading users won't get used to it. Many of > them are newcomers and beginners. They don't usually follow the > conversations on the list. > > Perhaps it's because of my software developer experience, but I am strongly > and seriously against abbreviations and acronyms in any case. Reading and > interpreting abbreviated text needs much more overhead than what you gain > during write time. Not to mention better text editors where you can define > abbreviations thus eliminating write time overhead. After having read the whole thread, I second your suggestion to drop all acronyms for our manuals names. If we doc writers and developers can figure out almost instantly what these acronyms mean when talking on -devel list, then we ne don't need them in the documentation index either; moreover, on my Linux box with Firefox 3 this page looks good with a 800 pixels screen width only if we remove those acronyms, so I will remove them unless there is any serious objection. If we ever need to remember the meaning of one acronym, a quick glance at the titles in the documentation index is enough. Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Absolute vs. relative pitches
2008/8/13 Trevor Daniels <[EMAIL PROTECTED]>: > This is a neat technique if the notes lie largely > in the same octave, but \transpose is not introduced > in the Learning Manual, so it can't be used there > without adding a fairly detailed section explaining > it first. > > Perhaps it could be mentioned in the Notation Reference > though. > > The Learning Manual is for learning users. They will > usually begin with a simple melody and relative mode > -is- easier for this, once you realize all you have to > do is count staff spaces. Counting staff spaces costs much brain power in melodies with big intervals (i.e. intervals bigger than a third). IMNSHO we *must* discuss absolute vs. relative pitches with usage cases in the Learning Manual. This is probably too early to do this in chapter 3 "Fundamental concepts" (although I intend to prepare the mind of the reader with a correction I added recently ;-), but this could be done in chapter 5 "Working with LilyPond files". Trevor, I put this on my TODO for after 2.12, unless you have any objection. Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Comments on Learning Manual 3 -- Fundamental concepts
2008/8/11 Graham Percival <[EMAIL PROTECTED]>: > On Sat, 9 Aug 2008 23:54:44 +0200 > "Valentin Villenave" <[EMAIL PROTECTED]> wrote: >> Actually, this is a Johnism (I don't know why he keeps asking us to >> remove parentheses). > > Parentheses are discouraged in highly formal writing, but they add > clarity and the docs aren't extremely formal, so let's use them. It's true that I excessively want to remove parentheses everywhere, and I agree parentheses are useful and add clarity for short phrases. However, using parentheses to enclose long phrases or even full sentences is poor in formal writing, in this case long dashes or footnotes are preferable. Our docs should follow formal writing, especially in NR, even if we can be more tolerant in LM. BTW good references for French typography discourage use of parentheses too, so I'm not very tolerant in this respect in French translations. >> What I have in mind when commenting an .itely file is that comments >> may be useful for the next documentation team (when the guys will >> start their own Grand Documentation Project in 10 years). >> In this specific case, theoretically doc writers are aware that the >> engraver is not used anymore... I'm afraid that some innocent docs writer is tempted to change back to Dynamic_engraver will check the Internals Reference first and see that this engraver is longer used in any context, although it still exists; that's why I left this comment in my commit, which doesn't cost much. Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Comments on Learning Manual 3 -- Fundamental concepts
2008/8/10 Trevor Daniels <[EMAIL PROTECTED]>: > Absolutely. When the LM was written the appropriate sections in the > NR did not exist, or at least the headings were expected to change. > Now the headings have stabilised (more or less) the refs can be added. > > Could you please make a new patch, taking into account the > comments made yesterday by others and push it to origin/master, > as you now have git access? I'm pretty happy with all your changes, > and the odd nit I can pick up afterwards. This will be easier than > trying to discuss little points in a long patch. Done, except that I forgot to add xrefs to NR in today's commits. I also pushed changes to the rest of LM 3, and will proofread LM 4 Tweaking output real soon. Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Comments on Learning Manual 3 -- Fundamental concepts
Hi Trevor, I proofread chapter 3 of the Learning Manual up to 3.1.4 'Modifying context properties'. This is globally great work, I wish I could read such docs instead of spending hours in trial-and-error and reading Mats' explanations on -user, when I started with LilyPond 4 years ago :-). I read it in Info format within Emacs, so I saw some issues with the way cross-references look; it might be useful to nitpick about this output format if we distribute Info docs with GUB later, and anyway LilyPond packages for GNU/Linux distros (e.g Fedora) certainly already include Info docs. I made many changes in a commit (patch attached), the detailed message gives motivation for some changes. After second thought, I think changes that intend to explain some details better are not welcome in LM, because it's not worth the effort for beginners making the effort to understand such details. Current explanations I propose to replace should probably remain intact: even if they simplify some details and are even sometimes a bit wrong, they are simple enough for beginners; if we go this way hiding details and lying a little, we must add 'See also' links to NR sections where details are well expained. If necessary, I can make a new patch to add to NR changes that can't be added to LM, and a new patch for LM3. What do you think? There are also two details below I'm not sure about. 3.1.2 Score is a (single) compound musical expression - """Start with the outer layer""" I thought that the common word for this was "level", but maybe "layer" makes more sense or is easier to understand. 3.2.1 I'm hearing Voices """the notes from the third and fourth voices are displaced to if necessary to avoid the note heads colliding.""" ^^ Is the first "to" intentional? (Oh, I'm not an English grammar specialist, you know, I probably sound like a dummy Frog here :-p) I'll come back again later with comments and changes on LM 3-4. Cheers, John 0004-Proofread-LM3-Fundamental-concepts-up-to-Modifying.patch Description: Binary data ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond under Leopard (and ccache)
On 2008/07/20 10:36 +0100, Alberto Simões wrote: > About compiling it from source: I made it. > > The problem was the use of ccache. I am not sure why, but lilypond build > system does not like it. So, if you are using ccache, it might be a good > idea to disable it. Which problem did ccache cause on your system? I've never had problems using ccache, though my computer is running GNU/Linux Fedora 9. Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: convert-ly...
On 2008/08/08 15:52 -0500, Stan Sanderson wrote: > > On 2008/07/08 09:42 -0500, Stan Sanderson wrote: > >> ...is not my friend. > >> > >> Mac OS 10.4.11, PPC, Lilypond 2.11.51 > >> > Additional info- > > I installed 2.11.51 (ppc version) on my Intel iMac running 10.5.4. > Convert-ly works on the iMac and the updated .ly file compiles > correctly (from the command line). I don't understand; what would make convert-ly fail on MacOS 1O.4 and work on Mac OS 10.5, if you say you have Python 2.5.2 on 10.4? (Maybe I should left this issue up to Mac users and developers, I've never got nor used a Mac.) Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: convert-ly...
On 2008/07/08 09:42 -0500, Stan Sanderson wrote:
> ...is not my friend.
>
> Mac OS 10.4.11, PPC, Lilypond 2.11.51
>
> convert-ly fails with the following messsage
> > @rule ((0, 1, 9), _ ('\\header { key = concat + with +
> > operator }'))
This is strange: does this unexpected linebreak also show in
convertrules.py? I have tested convert-ly from GUB binary version
2.11.51 for Linux x86 on a random file on Mutopia (version 2.0.1), and
it works for me.
Does it fail when you call it without command line arguments?
Otherwise, can you send an example file which makes convert-ly fail?
Cheers,
John
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
