another annoyance with `Dynamics' context

2009-12-11 Thread Werner LEMBERG
Thanks to Neil, TextSpanner items are now displayed in `Dynamics' contexts. However, this exhibits another serious annoyance, as shown in bug issue #928. This time, I've tagged my bug report with `medium'... Werner ___ lilypond-devel mailing li

Re: can't compile docs

2009-12-11 Thread Trevor Daniels
John Mandereau wrote 10 Dec 2009 Trevor Daniels wrote 9 Dec2009 Traceback (most recent call last): File "/home/trevor/lilypond-git/scripts/build/out/www_post", line 67, in map (os.mkdir, [os.path.join (out_root, d) for d in dirs]) OSError: [Errno 2] No such file or directory: 'out-www

extract_texi_filenames fail for contributor.xref-map out-of-tree build

2009-12-11 Thread Graham Percival
Doing an out-of-tree build: mkdir ../lily-out make distclean cd ../lily-out ../lilypond/configure make make doc produces a 0-byte contributor.xref-map and AAA-intro-reression.xref-map. It looks fine for INTALL, internals, snippets, usage, and web. (I'm surprised that it worked for we

Re: Can't compile docs

2009-12-11 Thread Trevor Daniels
Graham Percival wrote Thursday, December 10, 2009 1:40 AM On Wed, Dec 09, 2009 at 10:59:09PM +, Trevor Daniels wrote: Traceback (most recent call last): File "/home/trevor/lilypond-git/scripts/build/out/www_post", line 67, in map (os.mkdir, [os.path.join (out_root, d) for d in di

Re: extract_texi_filenames fail for contributor.xref-map out-of-tree build

2009-12-11 Thread John Mandereau
Le vendredi 11 décembre 2009 à 09:10 +, Graham Percival a écrit : > Doing an out-of-tree build: > mkdir ../lily-out > make distclean > cd ../lily-out > ../lilypond/configure > make > make doc > > produces a 0-byte contributor.xref-map I guess the problem might come from the lack o

Re: accent and marcato shouldn't be quantized

2009-12-11 Thread Graham Percival
On Thu, Dec 10, 2009 at 08:52:03PM -0800, Mark Polesky wrote: > Graham Percival wrote: > > It was added as a short-cut hack for > > << c1 {s4\< s s\> s\!} >> > > So then I assume you're okay with me de-quantizing the > espressivo as well. I have no objection to this. I confess that my vague re

Re: can't compile docs

2009-12-11 Thread John Mandereau
Le vendredi 11 décembre 2009 à 08:39 +, Trevor Daniels a écrit : > John, many thanks for your reply, but thankfully the problem > appears to have gone away. > > I modified www_post.py as you suggested, and then made a > clean start by running ./autogen.sh, make doc-clean and then > make doc in

Re: Build failure on OS X: "error: template class without a name"

2009-12-11 Thread Harmath Dénes
> Have you tried the suggested fix from the second thread? > > Something like > > sed -i 's|__vector|lily_vector|g' flower/include/std-vector.hh > > might be worth a try. > > Regards, > Neil You are right, according to http://www.mail-archive.com/fink-us...@lists.sourceforge.net/msg29281.htm

2.13.9 out

2009-12-11 Thread Graham Percival
2.13.9 has been uploaded and should be visible now. Could people give it a quick spin? NB: it is not visible on the main "download" page; you need to go directly to the "download site" link under "ancient versions". Alternately, go to the 2.13 docs -> (web) Community -> Download. Those links work

Re: Fix Tracker 918, Add extra RemoveEmpty*StaffContext functions to support "Frenched" scores (issue165096)

2009-12-11 Thread Ian Hulin
Hi Neil, n.putt...@gmail.com wrote: Hi Ian, LGTM, apart from some formatting issues and a few incorrect \version numbers. Can you sort out the naming of the new regression tests? For consistency with the existing test, I'd advise amending them as follows: hara-kiri-drumstaff.ly hara-kiri-rhy

Re: 2.13.9 out

2009-12-11 Thread John Mandereau
Le vendredi 11 décembre 2009 à 14:24 +, Graham Percival a écrit : > Quick poll: I promised to announce 2.13.9 on the info list (after > waiting 12-24 hours for tests to avoid any huge embarassment), but > it seems that the website still only displays 2.13.7. Who thinks > I should announce 2.13

Add option to indicate frets by letters in tablature

2009-12-11 Thread Trevor Daniels
I've just posted patch set 3 to Reitveld, after quite some struggles with juggling regression-testing and doc-building in a too-small virtual ubuntu system. See http://codereview.appspot.com/164063 The main change from patch set 2 is to generalise the input format of the context property fretLab

Re: 2.13.9 out

2009-12-11 Thread Trevor Daniels
Graham Percival wrote Friday, December 11, 2009 2:24 PM 2.13.9 has been uploaded and should be visible now. Could people give it a quick spin? Downloaded mingw and installed fine in Vista. Tested lilypond-book and lily by compiling notation/pitches.itely - fine convert-ly - fine Dropped a

Re: 2.13.9 out

2009-12-11 Thread Patrick McCarty
On Fri, Dec 11, 2009 at 6:24 AM, Graham Percival wrote: > > Quick poll: I promised to announce 2.13.9 on the info list (after > waiting 12-24 hours for tests to avoid any huge embarassment), but > it seems that the website still only displays 2.13.7.  Who thinks > I should announce 2.13.9 with the

Re: 2.13.9 out

2009-12-11 Thread John Mandereau
Le vendredi 11 décembre 2009 à 13:35 -0800, Patrick McCarty a écrit : > Do we know what's wrong with the website? Is this something I can help fix? No, as my previous reply probably shows, only somebody with a login on lilypond.org (and possibly privileges to update the makefiles and scripts in t

Re: UTF-8 support needs implementing to fix all bidi/rtl/ltr issues

2009-12-11 Thread Ted Walther
Thank you for filing that bug issue! How are things progressing? Also, can I make a $100 donation in gratitude to the person implementing the fix? Who is the responsible party to send the money to? Ted On Tue, Dec 08, 2009 at 03:14:43PM -0800, Patrick McCarty wrote: On Tue, Dec 8, 2009 at 5:

Re: UTF-8 support needs implementing to fix all bidi/rtl/ltr issues

2009-12-11 Thread Valentin Villenave
On Fri, Dec 11, 2009 at 11:44 PM, Ted Walther wrote: > Thank you for filing that bug issue!  How are things progressing?  Also, > can I make a $100 donation in gratitude to the person implementing the > fix?  Who is the responsible party to send the money to? I've added your bounty offer on the t

Re: accent and marcato shouldn't be quantized

2009-12-11 Thread Neil Puttock
2009/12/11 Mark Polesky : > Graham Percival wrote: >> It was added as a short-cut hack for >>   << c1 {s4\< s s\> s\!} >> > > So then I assume you're okay with me de-quantizing the > espressivo as well.  Is the attached patch okay to apply, LGTM. > do I need to do anything described in CG 8.7 "Ad

Re: Fix Tracker 918, Add extra RemoveEmpty*StaffContext functions to support "Frenched" scores (issue165096)

2009-12-11 Thread ian
Hi, I've implemented Neil's comments, re-run regression tests locally and uploaded amended patches to Rietveld. I think this should be ready to push now. Cheers, Ian http://codereview.appspot.com/165096/diff/1/2 File input/regression/hara-kiri-drums.ly (right): http://codereview.appspot.com/

Re: UTF-8 support needs implementing to fix all bidi/rtl/ltr issues

2009-12-11 Thread Patrick McCarty
On Fri, Dec 11, 2009 at 3:32 PM, Valentin Villenave wrote: > On Fri, Dec 11, 2009 at 11:44 PM, Ted Walther wrote: >> Thank you for filing that bug issue!  How are things progressing?  Also, >> can I make a $100 donation in gratitude to the person implementing the >> fix?  Who is the responsible p

Re: 2.13.9 out

2009-12-11 Thread Graham Percival
On Fri, Dec 11, 2009 at 08:47:47PM -, Trevor Daniels wrote: > > Graham Percival wrote Friday, December 11, 2009 2:24 PM > >> 2.13.9 has been uploaded and should be visible now. Could people >> give it a quick spin? > > Dropped a couple of files onto desktop icon - not so good > A log file was

Re: 2.13.9 out

2009-12-11 Thread Graham Percival
On Fri, Dec 11, 2009 at 01:35:24PM -0800, Patrick McCarty wrote: > On Fri, Dec 11, 2009 at 6:24 AM, Graham Percival > wrote: > > > > Quick poll: I promised to announce 2.13.9 on the info list (after > > waiting 12-24 hours for tests to avoid any huge embarassment), but > > it seems that the websit

Catching up on bugs

2009-12-11 Thread Graham Percival
With the release of 2.13.9, we now believe that all bugs are either fixed, or have been added to the issue tracker. If you have reported a bug and it is not in the tracker, please check the bug reporting guidelines and re-submit it. http://lilypond.org/doc/v2.13/Documentation/web/bug-reports V

Re: 2.13.9 out

2009-12-11 Thread Graham Percival
On Fri, Dec 11, 2009 at 06:02:45PM +0100, John Mandereau wrote: > Are you sure the last change in GNUmakefile has be updated in > the appropriate trusted-scripts/ directory on lilypond.org? Updating the GNUmakefile seems to have done it; apparently we forgot to do this. > PS: I sent you the Hunga

releases plans for Dec and 2010

2009-12-11 Thread Graham Percival
Just so that people know what's planned... - another beta for 2.12.3 will happen as soon as I can build the tests and docs. Jan and I will continue to work on this; hopefully it'll be out in a few days. This will be the last 2.12 release. - 2.13.10 will happen fairly soon thereafter; the main go

has issue #774 worked with a stable release?

2009-12-11 Thread Werner LEMBERG
Could someone please check issue #774 with a stable release (either 2.10 or 2.12) so that I can probably set the regression flag? At the time of my report, I only had 2.11.13 for comparison, which is a developer's version, and I still don't have any stable releases installed. Werner _

Re: releases plans for Dec and 2010

2009-12-11 Thread Joe Neeman
On Sat, 2009-12-12 at 07:00 +, Graham Percival wrote: > Just so that people know what's planned... > - another beta for 2.12.3 will happen as soon as I can build the tests > and docs. Jan and I will continue to work on this; hopefully it'll be > out in a few days. This will be the last 2.12 r

Re: has issue #774 worked with a stable release?

2009-12-11 Thread Patrick McCarty
On Fri, Dec 11, 2009 at 11:13 PM, Werner LEMBERG wrote: > > Could someone please check issue #774 with a stable release (either > 2.10 or 2.12) so that I can probably set the regression flag?  At the > time of my report, I only had 2.11.13 for comparison, which is a > developer's version, and I st