Re: only python 2.4 in scripts, please

2010-02-04 Thread John Mandereau
Le mercredi 03 février 2010 à 13:30 +, Graham Percival a écrit : > We officially only require python 2.4 for lilypond. Could the recent > change to ilypond-book.py be rewritten to avoid using the "any" > keyword introduced in 2.5 ? Oops, I used 'any' to avoid invoking 'startswith' string met

Re: [PATCH] bib2html: set TEXMFOUTPUT to the tempdir.

2010-02-04 Thread Graham Percival
Thanks, tested and applied. Cheers, - Graham On Tue, Feb 2, 2010 at 10:40 PM, Patrick McCarty wrote: > Hi, > > I need this patch for the latest updates to bibtex in TeX Live 2009 on > my machine.  LilyPond fails to compile the bibliographies without it. > > Here are the references for backgroun

Line breaking, simple-spacer, etc.

2010-02-04 Thread Boris Shingarov
I am experimenting with some modifications to the line breaking code, and I am stuck trying to understand how some of it works. So far my understanding is that Simple_spacer operates on a vector of Grobs, and it is a well-known Constrained-QP problem (rods = constraints, springs = quadratic fun

Re: Line breaking, simple-spacer, etc.

2010-02-04 Thread Joe Neeman
On Thu, 2010-02-04 at 15:33 -0500, Boris Shingarov wrote: > I am experimenting with some modifications to the line breaking code, > and I am stuck trying to understand how some of it works. So far my > understanding is that Simple_spacer operates on a vector of Grobs, and > it is a well-known Cons

Documentation NR 1.6.3 Instrument Names

2010-02-04 Thread Werner
In the NR of version "2.11.57" I found: Instrument names may be changed in the middle of a piece: \set Staff.instrumentName = "First" % \set Staff.shortInstrumentName = "one" c1 c c c \break c1 c c c \break \set Staff.instrumentName = "Second" % \set Staff.shortInstrum

Re: Documentation NR 1.6.3 Instrument Names

2010-02-04 Thread Graham Percival
On Thu, Feb 04, 2010 at 09:25:01PM +, Werner wrote: > In the NR of version "2.11.57" I found: Why are you look at that version? It's an UNSTABLE DEVELOPMENT version, which normal people should not be using. > Instrument names may be changed in the middle of a piece: > \set Staff.instru

Re: authors: anybody work on fonts?

2010-02-04 Thread Neil Puttock
On 2 February 2010 22:54, Graham Percival wrote: > I remember seeing some discussion and patches about fonts.  If I'm > not hallucinating, then any font-related contributor for 2.14 who > isn't an official developer should be listed in >  Documentation/included/authors.itexi > in the fontCurrent m

Re: Documentation NR 1.6.3 Instrument Names

2010-02-04 Thread Werner
Graham Percival percival-music.ca> writes: > On Thu, Feb 04, 2010 at 09:25:01PM +, Werner wrote: > > In the NR of version "2.11.57" I found: > > Why are you look at that version? It's an UNSTABLE DEVELOPMENT > version, which normal people should not be using. I used this version in the tim

Re: Documentation NR 1.6.3 Instrument Names

2010-02-04 Thread Werner
PS > I looked at the docu of this version, because I once downoaded it > completely so that I had it completely offline with working all > cross-references. For 2.13.11 I didn't find a possibility to > download such complete docu-packet. For online use the automatic language selection is reall

Re: Documentation NR 1.6.3 Instrument Names

2010-02-04 Thread Carl Sorensen
On 2/4/10 4:15 PM, "Werner" wrote: > Graham Percival percival-music.ca> writes: > >> On Thu, Feb 04, 2010 at 09:25:01PM +, Werner wrote: >>> In the NR of version "2.11.57" I found: >> >> Why are you look at that version? It's an UNSTABLE DEVELOPMENT >> version, which normal people shou

Re: Documentation NR 1.6.3 Instrument Names

2010-02-04 Thread Neil Puttock
On 4 February 2010 23:35, Carl Sorensen wrote: > I think that Werner has found a regression. > > See Notation Reference 1.6.3 for 2.12.  When the instrument name is changed, > the first staff after the change shows instrumentName, and succeeding staffs > show shortInstrumentName. That's a bug, w