Re: Issue 1229 in lilypond: Notes may be placed above clef and key signature.

2010-08-26 Thread lilypond
Comment #2 on issue 1229 by brownian.box: Notes may be placed above clef and key signature. http://code.google.com/p/lilypond/issues/detail?id=1229 the notes are on ledger lines, and the stems are up or down, or both up and down << { \key f \major a''4 a'' a'' a'' } \\ {

Re: Issue 1229 in lilypond: Notes may be placed above clef and key signature.

2010-08-26 Thread lilypond
Comment #1 on issue 1229 by Carl.D.Sorensen: Notes may be placed above clef and key signature. http://code.google.com/p/lilypond/issues/detail?id=1229 This happens when the width of the measure is greater than the line-width, the notes are on ledger lines, and the stems are up. Note that

Re: Issue 1235 in lilypond: Accidental overlays stem

2010-08-26 Thread lilypond
Comment #3 on issue 1235 by joeneeman: Accidental overlays stem http://code.google.com/p/lilypond/issues/detail?id=1235 By the way, the difficulty here is that there is a circular dependence. Stem length depends on beam formatting, which depends on horizontal layout, which depends on knowing

Re: Issue 1235 in lilypond: Accidental overlays stem

2010-08-26 Thread lilypond
Updates: Labels: -Priority-Critical -Regression Priority-Medium Comment #2 on issue 1235 by joeneeman: Accidental overlays stem http://code.google.com/p/lilypond/issues/detail?id=1235 Actually, accidentals collide with beams in 2.12 also; it's just a coincidence that it works for this

Re: Issue 1219 in lilypond: Broken tie may become a too small dot

2010-08-26 Thread lilypond
Comment #4 on issue 1219 by Carl.D.Sorensen: Broken tie may become a too small dot http://code.google.com/p/lilypond/issues/detail?id=1219 The slur is not necessary in order to show this problem. It appears to be caused by trying to fit more music in a bar than there is space for. If the

Re: Issue 1115 in lilypond: makelsr.py strips blank lines out of files; different behavior with full and local updates

2010-08-26 Thread lilypond
Updates: Status: Verified Comment #13 on issue 1115 by n.puttock: makelsr.py strips blank lines out of files; different behavior with full and local updates http://code.google.com/p/lilypond/issues/detail?id=1115 (No comment was entered for this change.)

Re: Issue 989 in lilypond: ensure that no information about 2.12.3 features is only in the regtests

2010-08-26 Thread lilypond
Comment #26 on issue 989 by n.puttock: ensure that no information about 2.12.3 features is only in the regtests http://code.google.com/p/lilypond/issues/detail?id=989 I've added "scheme" and "symbols and glyphs" to that snippet These aren't used in the docs. I've changed them to `rhythms'

Re: Issue 1096 in lilypond: ly:parser-parse-string segfaults when directly called at toplevel

2010-08-26 Thread lilypond
Updates: Status: Fixed Labels: fixed_2_13_32 Comment #26 on issue 1096 by n.puttock: ly:parser-parse-string segfaults when directly called at toplevel http://code.google.com/p/lilypond/issues/detail?id=1096 (No comment was entered for this change.) __

Re: Issue 1227 in lilypond: \autoBeamOff has no effect on other voices when used in a global variable/ghost voice.

2010-08-26 Thread lilypond
Updates: Status: Verified Comment #2 on issue 1227 by PhilEHolmes: \autoBeamOff has no effect on other voices when used in a global variable/ghost voice. http://code.google.com/p/lilypond/issues/detail?id=1227 NR now has the following: "The function of \autoBeamOff when used with \pa

Issue 1243 in lilypond: Regtest resgression - tie-direction-manual.ly

2010-08-26 Thread lilypond
Status: Accepted Owner: Labels: Type-Defect Priority-Critical Regression New issue 1243 by PhilEHolmes: Regtest resgression - tie-direction-manual.ly http://code.google.com/p/lilypond/issues/detail?id=1243 In the .31 regtests, the logfile has 2 new lines: "Unbound variable: open-file Unbou

Re: Regtest - difference from 13.30 to 13.31

2010-08-26 Thread Phil Holmes
"Joe Neeman" wrote in message news:aanlkti=4r=uuuswq7f80hfdx0xjb=ywguqr+p0ooa...@mail.gmail.com... On Wed, Aug 25, 2010 at 1:55 PM, Phil Holmes wrote: I'll be posting a few issues here over the next day or two, but a major difference between 2.13.30 and .31 is shown with page-spacing-tall-hea

Issue 1242 in lilypond: Regtest resgression - page-spacing-tall-headfoot.ly

2010-08-26 Thread lilypond
Status: Accepted Owner: Labels: Type-Defect Priority-Critical Regression New issue 1242 by PhilEHolmes: Regtest resgression - page-spacing-tall-headfoot.ly http://code.google.com/p/lilypond/issues/detail?id=1242 page-spacing-tall-headfoot.ly shows significantly different results between

Re: Issue 1162 in lilypond: website bibliography

2010-08-26 Thread lilypond
Updates: Status: Verified Comment #16 on issue 1162 by percival.music.ca: website bibliography http://code.google.com/p/lilypond/issues/detail?id=1162 Accents in those files can be done in issue 1241. ___ bug-lilypond mailing list bug-lilypon

Issue 1241 in lilypond: old .bib files contain latex-accents

2010-08-26 Thread lilypond
Status: Accepted Owner: Labels: Type-Documentation Priority-Postponed Maintainability Frog New issue 1241 by percival.music.ca: old .bib files contain latex-accents http://code.google.com/p/lilypond/issues/detail?id=1241 files in Documentation/essay/ contain latex-style accented characters.

Re: "content encoding error" in index of Notation

2010-08-26 Thread Graham Percival
On Thu, Aug 26, 2010 at 12:39:50PM +0200, Federico Bruni wrote: > And I've just noticed another bigger problem: all the manuals linked in > http://lilypond.org/website/manuals.html (the new website) > are the stable ones (v2.12, see the link). That's not a problem; 2.12 is the latest stable. It t

Re: "content encoding error" in index of Notation

2010-08-26 Thread Federico Bruni
I have a browser whose language is set to english, so I'm reading the english pages. And I've just noticed another bigger problem: all the manuals linked in http://lilypond.org/website/manuals.html (the new website) are the stable ones (v2.12, see the link). 2010/8/26 Francisco Vila > 2010/8/2

Re: "content encoding error" in index of Notation

2010-08-26 Thread Francisco Vila
2010/8/26 Federico Bruni : > If I open the index of Notation 2.13: > http://lilypond.org/doc/v2.13/Documentation/notation/lilypond-index > > I get the following error: > > > Content Encoding Error > > The page you are trying to view cannot be shown because it uses an invalid > or unsupported form o

"content encoding error" in index of Notation

2010-08-26 Thread Federico Bruni
If I open the index of Notation 2.13: http://lilypond.org/doc/v2.13/Documentation/notation/lilypond-index I get the following error: Content Encoding Error The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression. Does it happen to you as we

Re: Problem with 2.13.30?

2010-08-26 Thread Trevor Daniels
"Phil Holmes" wrote in message news:i53pqa$tp...@dough.gmane.org... "Trevor Daniels" wrote in message news:305ede3e0e3f4cdc926db8734c558...@trevorlaptop... However, I'm now back to my original problem first reported in http://lists.gnu.org/archive/html/lilypond-devel/2010-07/msg00063.html

Re: Issue 544 in lilypond: partial in polymetric fails

2010-08-26 Thread lilypond
Updates: Status: Verified Comment #5 on issue 544 by brownian.box: partial in polymetric fails http://code.google.com/p/lilypond/issues/detail?id=544 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org

Re: Issue 1162 in lilypond: website bibliography

2010-08-26 Thread lilypond
Comment #15 on issue 1162 by frederic...@m4x.org: website bibliography http://code.google.com/p/lilypond/issues/detail?id=1162 I was thinking at the essay: colorado.bib, computer-notation.bib and engravingbib.bib. ___ bug-lilypond mailing list bug

Re: Issue 382 in lilypond: misaligned nested \fill-lines

2010-08-26 Thread lilypond
Updates: Status: Verified Comment #4 on issue 382 by brownian.box: misaligned nested \fill-lines http://code.google.com/p/lilypond/issues/detail?id=382 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.o