Re: only python 2.4 in scripts, please
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 method with a list as an argument, which is new to Python 2.5, but overlooked the fact that 'any' was introduced in 2.5 too. This is now fixed in git. Sorry, John signature.asc Description: Ceci est une partie de message numériquement signée ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [PATCH] bib2html: set TEXMFOUTPUT to the tempdir.
Thanks, tested and applied. Cheers, - Graham On Tue, Feb 2, 2010 at 10:40 PM, Patrick McCarty pnor...@gmail.com 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 background on this issue: http://tug.org/pipermail/tlbuild/2010q1/001304.html http://bugs.archlinux.org/task/17978 Does the patch look okay? (I'm not very familiar with good/bad practices with respect to Python yet) Thanks, Patrick ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Line breaking, simple-spacer, etc.
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 function to minimize). What I don't understand is, if the spacer operates at the level of Grobs, which are built at an earlier stage in the pipeline, how are the changes necessitated by differences in line breaking, taken into account? in other words, if I take the last measure of a line and place it on the next line, it is not just a matter of literally moving that graphic to where the start of the next line is, but I also need to draw a clef, key signature, and possibly other fundamental things -- but at that stage in the rendering pipeline, is it not too late?? ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Line breaking, simple-spacer, etc.
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 Constrained-QP problem (rods = constraints, springs = quadratic function to minimize). What I don't understand is, if the spacer operates at the level of Grobs, which are built at an earlier stage in the pipeline, how are the changes necessitated by differences in line breaking, taken into account? in other words, if I take the last measure of a line and place it on the next line, it is not just a matter of literally moving that graphic to where the start of the next line is, but I also need to draw a clef, key signature, and possibly other fundamental things -- but at that stage in the rendering pipeline, is it not too late?? We create lots of extra grobs (eg. a BarNumber at every bar line) but most of them are not drawn. See the break-visibility property in item-interface. Cheers, Joe ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Documentation NR 1.6.3 Instrument Names
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.shortInstrumentName = two c1 c c c \break c1 c c c \break But this doesn't take effekt for me. The new instrumentname doesn't appear at all. (Only the shortname, if given, that means without the %, see above) Also tested in 2.13.11. ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Documentation NR 1.6.3 Instrument Names
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.instrumentName = First % \set Staff.shortInstrumentName = one c1 c c c \break c1 c c c \break \set Staff.instrumentName = Second % \set Staff.shortInstrumentName = two c1 c c c \break c1 c c c \break I sincerely doubt that the docs showed this example with commented-out lines. If it did, this was a temporary issue and would have been removed in 2.11.58. You should read the 2.12 docs. But this doesn't take effekt for me. The new instrumentname doesn't appear at all. (Only the shortname, if given, that means without the %, see above) That's exactly how instrumentName and shortInstrumentName work. Please re-read the very first paragraph of that subsection. Also tested in 2.13.11. It works in 2.13.12, as can be seen in the docs. I doubt that 2.13.11 was any different. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: authors: anybody work on fonts?
On 2 February 2010 22:54, Graham Percival gra...@percival-music.ca 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 macro. Yep, we've had two contributors outside the main developers; I've updated authors.itexi accordingly. Cheers, Neil ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Documentation NR 1.6.3 Instrument Names
Graham Percival graham at 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 time it was new. I looked at the docu aof this version, becaus 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. I sincerely doubt that the docs showed this example with commented-out lines. If it did, this was a temporary issue and would have been removed in 2.11.58. Of course it was shown without the % But this doesn't take effekt for me. The new instrumentname doesn't appear at all. (Only the shortname, if given, that means without the %, see above) That's exactly how instrumentName and shortInstrumentName work. Please re-read the very first paragraph of that subsection. I read it. But it's not clear. I my humble opinion the line \set Staff.instrumentName = #Second is nonsens, if it doesn't take effect at this place! It works in 2.13.12, as can be seen in the docs. I doubt that 2.13.11 was any different. In the 2.11.57 docu there really appeared once „Second“ followed by „two“ instead of two times „two“ in the docu now and in the reality now (and also if I put \version 2.11.57. That behavior would more useful for me. Greetings Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Documentation NR 1.6.3 Instrument Names
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 really annoying. I usually use german (browser-default), but for the lilypond-docu I prefer english. A solution, which remembers this, would be much better. (preferences-cookie for the lilypond-homepage?) Even following cross references out of one english site of the docu brings up a german site again and again... ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Documentation NR 1.6.3 Instrument Names
On 2/4/10 4:15 PM, Werner mey@web.de wrote: Graham Percival graham at 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 time it was new. I looked at the docu aof this version, becaus 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. I sincerely doubt that the docs showed this example with commented-out lines. If it did, this was a temporary issue and would have been removed in 2.11.58. Of course it was shown without the % But this doesn't take effekt for me. The new instrumentname doesn't appear at all. (Only the shortname, if given, that means without the %, see above) That's exactly how instrumentName and shortInstrumentName work. Please re-read the very first paragraph of that subsection. I read it. But it's not clear. I my humble opinion the line \set Staff.instrumentName = #Second is nonsens, if it doesn't take effect at this place! It works in 2.13.12, as can be seen in the docs. I doubt that 2.13.11 was any different. 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. In 2.13 it doesn't behave this way. I made a change to the docs, but I think I'll revert it now, since I see this as a bug. Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Documentation NR 1.6.3 Instrument Names
On 4 February 2010 23:35, Carl Sorensen c_soren...@byu.edu 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, which was fixed in 2.13.4 (see issue 452). Regards, Neil ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
