Re: Issue 1229 in lilypond: Notes may be placed above clef and key signature.
Updates:
Labels: -Priority-Critical Priority-High
Comment #3 on issue 1229 by joeneeman: Notes may be placed above clef and
key signature.
http://code.google.com/p/lilypond/issues/detail?id=1229
Not a regression from 2.12, although I agree that it's very ugly. The
following example produces the same output on 2.13 and 2.12:
\version "2.12.0"
<<
{
\key f \major
a'''4 a''' a''' a'''
}
\\
{
\key f \major
c4 c c c
}
\layout {
indent = 0
line-width = 2.2\cm
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1240 in lilypond: Music overflows page: #'((space . N) (stretchability . 0)) and nothing more with spacings
Updates: Status: Started Owner: joeneeman Comment #3 on issue 1240 by joeneeman: Music overflows page: #'((space . N) (stretchability . 0)) and nothing more with spacings http://code.google.com/p/lilypond/issues/detail?id=1240 Patch here: http://codereview.appspot.com/2065041/ There are some pretty ugly hacks (like creating a dummy Paper_column in System::get_pure_bound in order to do a binary search on all paper columns), so I'm hoping someone has better suggestions... ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1242 in lilypond: Regtest resgression - page-spacing-tall-headfoot.ly
Updates: Status: Fixed Labels: fixed_2_13_32 Comment #1 on issue 1242 by joeneeman: Regtest resgression - page-spacing-tall-headfoot.ly http://code.google.com/p/lilypond/issues/detail?id=1242 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 894 in lilypond: lilypond-book fails from the command-line in OSX 10.4
Updates: Status: Fixed Comment #18 on issue 894 by percival.music.ca: lilypond-book fails from the command-line in OSX 10.4 http://code.google.com/p/lilypond/issues/detail?id=894 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1167 in lilypond: link from 2.13 manuals HTML pages back to website
Updates: Summary: link from 2.13 manuals HTML pages back to website Status: Fixed Labels: fixed_2_13_32 Comment #7 on issue 1167 by percival.music.ca: link from 2.13 manuals HTML pages back to website http://code.google.com/p/lilypond/issues/detail?id=1167 The links for 2.12 manuals is now part of 1244. I believe that the links for the 2.13 manuals will be fixed in 2.13.32 with commit 5e040cd922e5cdae777d3a8a16fc9dd80d24a6ef , but this needs verification at http://lilypond.org/website/development.html after .32 is out. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1038 in lilypond: more technical website items
Updates: Status: Verified Comment #5 on issue 1038 by percival.music.ca: more technical website items http://code.google.com/p/lilypond/issues/detail?id=1038 Oops, forgot to mention: the changeover is now issue 1244. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1038 in lilypond: more technical website items
Updates: Status: Fixed Comment #4 on issue 1038 by percival.music.ca: more technical website items http://code.google.com/p/lilypond/issues/detail?id=1038 I've just verified that the goals are working in google analytics. The symlink issue can only be done after the changeover. I'm verifying this myself because the Bug Squad doesn't have access to analytics. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1244 in lilypond: Change to the new website
Status: Accepted Owner: Labels: Type-Build Priority-Critical website New issue 1244 by percival.music.ca: Change to the new website http://code.google.com/p/lilypond/issues/detail?id=1244 A few items can only be done once we finally change over. This is planned to happen with the first "alpha" version of 2.14. These items can only be done after the switch: 1) Make sure the short links / .htaccess redirects are good after switching to /website/ instead of /web/. 2) On 29 May 2009, francisco reported that the doc redirect pointed to .../Documentation/index.html, which skips over the automatic language selection. Point to .../Documentation/ instead. In other words, make sure that Documentation/web/servers/lilypond.org.htaccess doesn't contain any ".html" for normal stuff. 3) The "back to documentation index" link in the 2.12 docs should end up at /website/manuals.html. This will be done by manually adding a redirect or symlink, which will be removed when 2.14 is out. The exact instructions for this will be added to the CG. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1182 in lilypond: Website rendering problem with navigation bar in IE 6
Comment #6 on issue 1182 by percival.music.ca: Website rendering problem with navigation bar in IE 6 http://code.google.com/p/lilypond/issues/detail?id=1182 FWIW, in the last month we had: - 73% visits from IE 8.x - 18% visits from IE 7.x - 9% visits from IE 6.x - 0% visits from IE 5.x (rounded to the nearest %) IE was 16% of our overall views, so 1.5% of our visitors use IE 6. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 989 in lilypond: ensure that no information about 2.12.3 features is only in the regtests
Updates: Status: Fixed Labels: fixed_2_13_32 Comment #28 on issue 989 by percival.music.ca: ensure that no information about 2.12.3 features is only in the regtests http://code.google.com/p/lilypond/issues/detail?id=989 Neil: technically the "one last look" should be done in the "verifying" phase, so there's no problem marking this "fixed". James: because there were so many people working on this -- and in particular, given the confusion at the beginning between Valentin and then nobody and then me for a bit and then Phil but he was learning and oops apparently LSR snippets need to be tagged with "docs" **and** something else and then etc -- I don't think that asking for another "review" is casting doubt on any one person's abilities. ... that said, I can't see it being worth spending hours verifying this particular issue, given that 1217 is almost the same. In particular, any time spent working on 989 would be better spent on 1217. So I propose, as release manager, that we skip the "verification" for this issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 989 in lilypond: ensure that no information about 2.12.3 features is only in the regtests
Comment #27 on issue 989 by pkx1...@hotmail.com: ensure that no information about 2.12.3 features is only in the regtests http://code.google.com/p/lilypond/issues/detail?id=989 ? All the reg tests were listed, and as I (and others) docced them the list was reviewed by Phil who removed the reg tests from the wiki and left those that needed to be done. It was because no one was looking thoroughly through them that this tracker item took so long to do. However I think Phil has done this and can only say that waiting until 'someone' else does it is a waste of time. I mean, what does it take to get a tracker item approved? ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 684 in lilypond: Enhancement: MetronomeMark should support break-align-symbols
Updates: Status: Fixed Comment #26 on issue 684 by jan.nieuwenhuizen: Enhancement: MetronomeMark should support break-align-symbols http://code.google.com/p/lilypond/issues/detail?id=684 Fixed, as per - http://codereview.appspot.com/1579041 One niggle/=feature request wrt multi-measure-rest placement remains. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: "content encoding error" in index of Notation
2010/8/26 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 took me about > 10 hours to get all the links to 2.12 working given the change of > manual names and dirs, and there's still one issue remaining. > Ok, I see. Anyway, now I'm using a different laptop and connection and I don't have the "content encoding error" anymore. So it was probably something about the bad internet connection I had yesterday. Sorry for the noise ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
