Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14
Comment #12 on issue 1683 by carl.d.s...@gmail.com: The dynamic m is broken at staff-size-14 http://code.google.com/p/lilypond/issues/detail?id=1683 feta-alphabet14 uses a design size of 14.14. When I use this design size, I get the defective m. If I use 14.15 or 14.13, I don't get the defective m. I find the defective m by looking at mf/out/feta-alphabet14.pfb using fontforge. my mf2pt1 is version 2.4.4 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14
Comment #11 on issue 1683 by carl.d.s...@gmail.com: The dynamic m is broken at staff-size-14 http://code.google.com/p/lilypond/issues/detail?id=1683 I got started on this bug because it was reported on the debian list. I'll do some more looking into this. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14
Updates: Labels: -Priority-High Priority-Critical Comment #10 on issue 1683 by percival.music.ca: The dynamic m is broken at staff-size-14 http://code.google.com/p/lilypond/issues/detail?id=1683 I cannot reproduce with current git local build, but I don't believe that Carl is insane. I see a distorted "m" when viewing the pdf that Carl supplied. So it's not a pdf viewer issue; the pdf which he produces are different from the ones that I produce, using with 2.14.0 GUB or current git. I don't know whether to point fingers at fontforge not being compiled with --enable-double, or ghostscript, or fontconfig, or what... but clearly there's something very wrong here. I'm marking this as Critical. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 34 in lilypond: Grace synchronization
Comment #13 on issue 34 by carlo.stemberger: Grace synchronization http://code.google.com/p/lilypond/issues/detail?id=34 Debian issues #153782 and #153784 are forwarded here. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=153782 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=153784 Regards, Carlo ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14
Comment #9 on issue 1683 by lemzw...@googlemail.com: The dynamic m is broken at staff-size-14 http://code.google.com/p/lilypond/issues/detail?id=1683 I'm always building FontForge by myself: Executable based on sources from 23:14 GMT 25-Feb-2011-ML-TtfDb-D. Library based on sources from 13:48 GMT 22-Feb-2011. fontforge 20110225 libfontforge 20110222-ML ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14
Updates: Status: Accepted Comment #8 on issue 1683 by carl.d.s...@gmail.com: The dynamic m is broken at staff-size-14 http://code.google.com/p/lilypond/issues/detail?id=1683 Reproduced also in 2.15.1 with local build. Here's my fontforge info: sorensen2:lilypond Carl$ fontforge --version Copyright (c) 2000-2010 by George Williams. Executable based on sources from 11:21 GMT 1-May-2010-ML. Library based on sources from 03:43 GMT 29-Apr-2010. fontforge 20100501 libfontforge 20100429-ML ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: LSR Snippet in Doc needs modifying
On Tue, Jun 07, 2011 at 06:05:50PM +, James Lowe wrote: > Thanks, I assume that means it will propagate into the doc automagically? Not automatically, but it's part of a usual process done by other people. Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14
Comment #7 on issue 1683 by tdaniels...@googlemail.com: The dynamic m is broken at staff-size-14 http://code.google.com/p/lilypond/issues/detail?id=1683 It's fine in the 2.14.0 GUB release for Windows running under Vista and viewed with Acrobat Reader Ver 10.0.1 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
RE: LSR Snippet in Doc needs modifying
Thanks, I assume that means it will propagate into the doc automagically? As it isn't in snippets/new I have nothing to run the .py script on. James PS that's one bit of the Doc that I am still rusty on as I don't need to touch snippets that often so have forgotten most of what we did last year for that reg test marathon :) )-Original Message- )From: bug-lilypond-bounces+james.lowe=datacore@gnu.org )[mailto:bug-lilypond-bounces+james.lowe=datacore@gnu.org] On )Behalf Of Phil Holmes )Sent: 07 June 2011 18:22 )To: bug-lilypond@gnu.org )Subject: Re: LSR Snippet in Doc needs modifying ) )"James Lowe" wrote in message )news:DDFAF00DC0C80042BAB7BBA1B3838AF9146B57F2@Mail- )FTL1.datacoresoftware.com... )> Hello, )> )> Specifically )> )> 'Use square bracket at the start of a staff group' )> )> This uses an incorrect context name )> )> ' ChoirStaffGroup' it should be 'ChoirStaff' )> )> I don't have edit permissions, so could someone update the snippet? )> )> Thanks )> )> James ) )There you go. ) )-- )Phil Holmes )Bug Squad ) ) ) ) )___ )bug-lilypond mailing list )bug-lilypond@gnu.org )https://lists.gnu.org/mailman/listinfo/bug-lilypond ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14
Comment #6 on issue 1683 by carl.d.s...@gmail.com: The dynamic m is broken at staff-size-14 http://code.google.com/p/lilypond/issues/detail?id=1683 Saw it on both Preview and Acrobat Reader. I haven't checked FontForge. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14
Comment #5 on issue 1683 by lemzw...@googlemail.com: The dynamic m is broken at staff-size-14 http://code.google.com/p/lilypond/issues/detail?id=1683 or dependent on the FontForge version? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1684 in lilypond: CueClefs: Use middleCClefPosition in the key engraver
Status: Accepted Owner: Labels: Type-Enhancement Priority-Medium New issue 1684 by percival.music.ca: CueClefs: Use middleCClefPosition in the key engraver http://code.google.com/p/lilypond/issues/detail?id=1684 http://codereview.appspot.com/4551101 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14
Comment #4 on issue 1683 by pkx1...@gmail.com: The dynamic m is broken at staff-size-14 http://code.google.com/p/lilypond/issues/detail?id=1683 or PDF viewer specific? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1217 in lilypond: clean up undocumented regtests in 2.14.0.
Comment #3 on issue 1217 by pkx1...@gmail.com: clean up undocumented regtests in 2.14.0. http://code.google.com/p/lilypond/issues/detail?id=1217 Phil, do you want to do what we did last time? Use that Wiki to list what we need to do (if anything) so I can eaisly keep track of my progress? That seemed to work quite well for 989 and is less messy than a single thread like this. There may be not that much to do - I know footnotes is one and I'm just finishing up \cueClef, so those are two that I know about off the top of my head - assuming RK has added his reg tests yet. james ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14
Comment #3 on issue 1683 by carl.d.s...@gmail.com: The dynamic m is broken at staff-size-14 http://code.google.com/p/lilypond/issues/detail?id=1683 Hmm -- I reproduce it on stable/2.14. Is it maybe OS specific? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1568 in lilypond: ENHANCEMENT: Adds the Articulate script with documentation
Comment #2 on issue 1568 by paconet@gmail.com: ENHANCEMENT: Adds the Articulate script with documentation http://code.google.com/p/lilypond/issues/detail?id=1568 More or less. The Rietveld patch was applied and includes the script and basic documentation. Then I promised to (with time) add a number of documents provided by Dr Peter Chubb. This could be another issue or reuse the same. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: LSR Snippet in Doc needs modifying
"James Lowe" wrote in message news:ddfaf00dc0c80042bab7bba1b3838af9146b5...@mail-ftl1.datacoresoftware.com... Hello, Specifically 'Use square bracket at the start of a staff group' This uses an incorrect context name ' ChoirStaffGroup' it should be 'ChoirStaff' I don't have edit permissions, so could someone update the snippet? Thanks James There you go. -- Phil Holmes Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1682 in lilypond: Website version links need updating
Updates: Labels: website Comment #2 on issue 1682 by percival.music.ca: Website version links need updating http://code.google.com/p/lilypond/issues/detail?id=1682 also: this can (and should) be tested with make website instead of the make doc. I mean, make doc would work, but make website takes 3 minutes instead of 120 minutes, so it just makes sense. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1171 in lilypond: docs search box always does 2.14
Updates: Summary: docs search box always does 2.14 Labels: -Priority-High Priority-Medium Comment #1 on issue 1171 by percival.music.ca: docs search box always does 2.14 http://code.google.com/p/lilypond/issues/detail?id=1171 I've changed this to 2.14. The hard-coding is still unfortunate, and the problem in the doc build (instead of website build) is unfortunate, but it's not high priority. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1496 in lilypond: Update Pango to 1.28.3
Updates: Labels: -Priority-High Priority-Medium Comment #10 on issue 1496 by percival.music.ca: Update Pango to 1.28.3 http://code.google.com/p/lilypond/issues/detail?id=1496 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 982 in lilypond: web big-html and pdf look bad
Updates: Labels: -Priority-High Priority-Medium Comment #1 on issue 982 by percival.music.ca: web big-html and pdf look bad http://code.google.com/p/lilypond/issues/detail?id=982 we've lived for a year with this. It can't be all that important. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1568 in lilypond: ENHANCEMENT: Adds the Articulate script with documentation
Updates: Status: Fixed Comment #1 on issue 1568 by percival.music.ca: ENHANCEMENT: Adds the Articulate script with documentation http://code.google.com/p/lilypond/issues/detail?id=1568 I believe this was finished a few weeks ago? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1567 in lilypond: Add documentation for footnotes
Updates: Labels: -Priority-High Priority-Medium Comment #3 on issue 1567 by percival.music.ca: Add documentation for footnotes http://code.google.com/p/lilypond/issues/detail?id=1567 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1217 in lilypond: clean up undocumented regtests in 2.14.0.
Updates: Labels: -Priority-High Priority-Medium Comment #2 on issue 1217 by percival.music.ca: clean up undocumented regtests in 2.14.0. http://code.google.com/p/lilypond/issues/detail?id=1217 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1213 in lilypond: Segmentation fault : extender triggers an infinite loop in Context::now_mom ()
Updates: Status: Fixed Comment #3 on issue 1213 by percival.music.ca: Segmentation fault : extender triggers an infinite loop in Context::now_mom () http://code.google.com/p/lilypond/issues/detail?id=1213 cannot reproduce in 2.14.0. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1658 in lilypond: Doc: need documentation of \cueClef and \cueDuringWithClef
Updates: Labels: -Priority-High Priority-Medium Comment #7 on issue 1658 by percival.music.ca: Doc: need documentation of \cueClef and \cueDuringWithClef http://code.google.com/p/lilypond/issues/detail?id=1658 to avoid clutter, I'm cleaning up some priorities. There's no way this is High. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1682 in lilypond: Website version links need updating
Comment #1 on issue 1682 by percival.music.ca: Website version links need updating http://code.google.com/p/lilypond/issues/detail?id=1682 In addition, the MacOS and Windows examples have wrong versions in their screen shots. good catch, but I don't think we want to update those version numbers for each stable version. There's no harm in having a lower version number for simple pieces. The unix example is really bad, because if somebody copies&pastes that example (like we tell them to), lilypond will give an error due to the version number. We don't want people's first glimpse of lilypond to be an error. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs in Debian
Thank you Carl! > 143709 is invalid. > 153782 is invalid. > 153784 is invalid. Why? > 437267 has been fixed in 2.14. Ok, tagged. > 607431 is accepted as lilypond issue 1683. Ok, forwarded. > 139577 has been fixed. Ok. Closed. > 335828 is a Debian bug, not a LilyPond bug. Ok. > 98659 has been fixed. Ok. Closed. Ciao! Carlo ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 977 in lilypond: GUB build numbers
Updates: Labels: -Priority-High Priority-Medium Comment #2 on issue 977 by percival.music.ca: GUB build numbers http://code.google.com/p/lilypond/issues/detail?id=977 meh, we don't really need build numbers. Downgrading priority. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14
Updates: Status: Invalid Comment #2 on issue 1683 by percival.music.ca: The dynamic m is broken at staff-size-14 http://code.google.com/p/lilypond/issues/detail?id=1683 Cannot reproduce with 2.14.0. Don't care about 2.12.3. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
LSR Snippet in Doc needs modifying
Hello, Specifically 'Use square bracket at the start of a staff group' This uses an incorrect context name ' ChoirStaffGroup' it should be 'ChoirStaff' I don't have edit permissions, so could someone update the snippet? Thanks James ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs in Debian
On 6/7/11 5:42 AM, "Carlo Stemberger" wrote: > The Debian Bug Tracking System contains some bug reports concerning LilyPond, > with short examples. > > http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=lilypond;dist=unstable > > Could you verify them and in case add them to your track, please? > > Thank you! Carlo, 143709 is invalid. 153782 is invalid. 153784 is invalid. 437267 has been fixed in 2.14. 607431 is accepted as lilypond issue 1683. 139577 has been fixed. 335828 is a Debian bug, not a LilyPond bug. 98659 has been fixed. Hope this helps. Carl ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1683 in lilypond: The dynamic m is broken at staff-size-14
Status: Accepted
Owner:
New issue 1683 by carl.d.s...@gmail.com: The dynamic m is broken at
staff-size-14
http://code.google.com/p/lilypond/issues/detail?id=1683
The dynamic m is broken at staff size 14.
\version "2.12.3"
#(set-global-staff-size 14)
\book {
% this is the problematic symbol
\markup{ \dynamic "m" }
}
Attachments:
m14.pdf 16.6 KB
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14
Updates: Labels: Type-Defect Priority-High Comment #1 on issue 1683 by carl.d.s...@gmail.com: The dynamic m is broken at staff-size-14 http://code.google.com/p/lilypond/issues/detail?id=1683 Perhaps this should even be Critical ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: CHANGES -> 2.14 instead of 2.13
2011/6/7 Graham Percival : > On Tue, Jun 07, 2011 at 02:14:39PM +0200, Francisco Vila wrote: >> 2011/6/7 Graham Percival : >> > On Tue, Jun 07, 2011 at 01:33:39PM +0200, Francisco Vila wrote: >> >> BTW http://lilypond.org/changes.es.html has broken links to both >> >> split+bigpage Changes page. PDF link is right. >> >> Other languages show a mix of broken links and English pages. >> > >> > Well, if >> > http://lilypond.org/doc/v2.14/Documentation/changes/index.es.html >> > is the wrong url, then what's the right one? >> >> It is not that easy. You know that we do not write urls in web >> texinfo files. The resulting URL is a crazy combination of refs, >> macros, post processing and luck. In my offline copy, split link does >> work, bigpage link doesn't. > > I know. I'm not asking for a fix. I'm asking what the online URL > is of the changes document in spanish. > >> In http://lilypond.org/doc/v2.14/Documentation/web/changes.es.html , >> links do work. > > On that webpage, the html links go to English changes; only the > pdf link goes to Spanish. If you're happy with that, then I can > make the website do the same thing. I think the Spanish page is not being generated, so yes, linking to English as other languages do is the next bad thing. A Spanish PDF is being generated and correctly linked; therefore, please, if any, change only the two first link refs. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs in Debian
Thank you, Colin. If you find something useful please let me know. Ciao! Carlo ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2.14 linux download page error
On 11-06-07 04:32 AM, Graham Percival wrote: On Tue, Jun 07, 2011 at 07:41:57AM +1000, Nick Payne wrote: The "compiling a file" example on the right-hand side of the download page (http://lilypond.org/unix.html) has a version number in the sample ly file of 2.15.0. Should be 2.14.0. Please send such messages to bug-lilypond. Bug Squad: when you add it to the tracker, please add a warning from me that fixing this includes 2-3 "gotchas". Each "gotcha" could easily waste an hour of time, or could be resolved by sending a 2-sentence email to me. Anybody working on this should contact me if they get stuck for longer than 10 minutes on any step. Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond Added as issue 1682. Colin -- A chief event of life is the day in which we have encountered a mind that startled us. -Ralph Waldo Emerson, writer and philosopher (1803-1882) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1682 in lilypond: Website version links need updating
Status: Accepted Owner: Labels: Type-Documentation Priority-High New issue 1682 by colinpkc...@gmail.com: Website version links need updating http://code.google.com/p/lilypond/issues/detail?id=1682 On Tue, Jun 07, 2011 at 07:41:57AM +1000, Nick Payne wrote: > The "compiling a file" example on the right-hand side of the > download page (http://lilypond.org/unix.html) has a version number > in the sample ly file of 2.15.0. Should be 2.14.0. Please send such messages to bug-lilypond. Bug Squad: when you add it to the tracker, please add a warning from me that fixing this includes 2-3 "gotchas". Each "gotcha" could easily waste an hour of time, or could be resolved by sending a 2-sentence email to me. Anybody working on this should contact me if they get stuck for longer than 10 minutes on any step. Cheers, - Graham In addition, the MacOS and Windows examples have wrong versions in their screen shots. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs in Debian
On 11-06-07 05:42 AM, Carlo Stemberger wrote: The Debian Bug Tracking System contains some bug reports concerning LilyPond, with short examples. http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=lilypond;dist=unstable Could you verify them and in case add them to your track, please? Thank you! Carlo ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond Thanks, Carl. I'll have a look over the list and add anything that is new to us. Colin -- A chief event of life is the day in which we have encountered a mind that startled us. -Ralph Waldo Emerson, writer and philosopher (1803-1882) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: CHANGES -> 2.14 instead of 2.13
On Tue, Jun 07, 2011 at 02:14:39PM +0200, Francisco Vila wrote: > 2011/6/7 Graham Percival : > > On Tue, Jun 07, 2011 at 01:33:39PM +0200, Francisco Vila wrote: > >> BTW http://lilypond.org/changes.es.html has broken links to both > >> split+bigpage Changes page. PDF link is right. > >> Other languages show a mix of broken links and English pages. > > > > Well, if > > http://lilypond.org/doc/v2.14/Documentation/changes/index.es.html > > is the wrong url, then what's the right one? > > It is not that easy. You know that we do not write urls in web > texinfo files. The resulting URL is a crazy combination of refs, > macros, post processing and luck. In my offline copy, split link does > work, bigpage link doesn't. I know. I'm not asking for a fix. I'm asking what the online URL is of the changes document in spanish. > In http://lilypond.org/doc/v2.14/Documentation/web/changes.es.html , > links do work. On that webpage, the html links go to English changes; only the pdf link goes to Spanish. If you're happy with that, then I can make the website do the same thing. Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: CHANGES -> 2.14 instead of 2.13
2011/6/7 Graham Percival : > On Tue, Jun 07, 2011 at 01:33:39PM +0200, Francisco Vila wrote: >> BTW http://lilypond.org/changes.es.html has broken links to both >> split+bigpage Changes page. PDF link is right. >> Other languages show a mix of broken links and English pages. > > Well, if > http://lilypond.org/doc/v2.14/Documentation/changes/index.es.html > is the wrong url, then what's the right one? It is not that easy. You know that we do not write urls in web texinfo files. The resulting URL is a crazy combination of refs, macros, post processing and luck. In my offline copy, split link does work, bigpage link doesn't. In http://lilypond.org/doc/v2.14/Documentation/web/changes.es.html , links do work. If I change the source, for sure I am fixing a link just to break another. That has a solution or another, but finding it requires more time than I currently have. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Bugs in Debian
The Debian Bug Tracking System contains some bug reports concerning LilyPond, with short examples. http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=lilypond;dist=unstable Could you verify them and in case add them to your track, please? Thank you! Carlo ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: CHANGES -> 2.14 instead of 2.13
On Tue, Jun 07, 2011 at 01:33:39PM +0200, Francisco Vila wrote: > BTW http://lilypond.org/changes.es.html has broken links to both > split+bigpage Changes page. PDF link is right. > Other languages show a mix of broken links and English pages. Well, if http://lilypond.org/doc/v2.14/Documentation/changes/index.es.html is the wrong url, then what's the right one? Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: CHANGES -> 2.14 instead of 2.13
2011/6/7 Graham Percival : > On Tue, Jun 07, 2011 at 12:55:08PM +0200, Francisco Vila wrote: >> > It looks easy to fix this; however, the string is intended to show new >> > features in current development since latest stable. When 2.15 comes >> > out, it should be changed to "2.15 since 2.14". >> >> Patch attached. > > Already done on master for the English docs, but not for > translations. Done in Spanish and pushed to master. Other languages don't have this file translated. BTW http://lilypond.org/changes.es.html has broken links to both split+bigpage Changes page. PDF link is right. Other languages show a mix of broken links and English pages. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: CHANGES -> 2.14 instead of 2.13
On Tue, Jun 07, 2011 at 12:55:08PM +0200, Francisco Vila wrote: > > It looks easy to fix this; however, the string is intended to show new > > features in current development since latest stable. When 2.15 comes > > out, it should be changed to "2.15 since 2.14". > > Patch attached. Already done on master for the English docs, but not for translations. Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: CHANGES -> 2.14 instead of 2.13
2011/6/7 Francisco Vila : > 2011/6/7 Xavier Scheuer : >> On 7 June 2011 09:37, Xavier Scheuer wrote: >>> Congratulations for the release of 2.14! >>> >>> CHANGES is showing "New features in 2.13 since 2.12". >>> Shoudln't it be updated to ""New features in 2.14" etc. ? > > It looks easy to fix this; however, the string is intended to show new > features in current development since latest stable. When 2.15 comes > out, it should be changed to "2.15 since 2.14". Patch attached. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com From b6f88e1a4da9aa7289ce3b69a55661813995111c Mon Sep 17 00:00:00 2001 From: Francisco Vila Date: Tue, 7 Jun 2011 12:54:28 +0200 Subject: [PATCH] Say 2.14 since 2.12 in Changes. --- Documentation/changes.tely|2 +- Documentation/es/changes.tely |2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/changes.tely b/Documentation/changes.tely index 150f603..d61f0fc 100644 --- a/Documentation/changes.tely +++ b/Documentation/changes.tely @@ -36,7 +36,7 @@ See user manual, \NAME\ @finalout @node Top -@top New features in 2.13 since 2.12 +@top New features in 2.14 since 2.12 @allowcodebreaks false diff --git a/Documentation/es/changes.tely b/Documentation/es/changes.tely index ae6370d..905a6af 100644 --- a/Documentation/es/changes.tely +++ b/Documentation/es/changes.tely @@ -44,7 +44,7 @@ Véase el manual del usuario, \NAME\ @finalout @node Top -@top Funcionalidades nuevas de la versión 2.13 desde la 2.12 +@top Funcionalidades nuevas de la versión 2.14 desde la 2.12 @allowcodebreaks false -- 1.7.0.4 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: CHANGES -> 2.14 instead of 2.13
2011/6/7 Xavier Scheuer : > On 7 June 2011 09:37, Xavier Scheuer wrote: >> Congratulations for the release of 2.14! >> >> CHANGES is showing "New features in 2.13 since 2.12". >> Shoudln't it be updated to ""New features in 2.14" etc. ? It looks easy to fix this; however, the string is intended to show new features in current development since latest stable. When 2.15 comes out, it should be changed to "2.15 since 2.14". -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1658 in lilypond: Doc: need documentation of \cueClef and \cueDuringWithClef
Comment #6 on issue 1658 by pkx1...@gmail.com: Doc: need documentation of \cueClef and \cueDuringWithClef http://code.google.com/p/lilypond/issues/detail?id=1658 I think we may be able to use the 'line break' example as a snippet if needed else I'll make an @lilypond. But I can make a simple enough @lilypond example for the other. So don't add any snippets yet. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Website doc search still using 2.12
On Tue, Jun 07, 2011 at 09:41:38AM +0200, Xavier Scheuer wrote: > If we use the search box in the bottom of the left panel in the > Notation Reference, it makes a google search with > > site:lilypond.org +v2.12 mysearch > > Should it be changed to > > site:lilypond.org +v2.14 mysearch > > since 2.14 is now the latest stable version? Thanks, fixed in git. Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1672 in lilypond: patch Allows LilyPond to ignore certain note-heads in a stem
Updates: Status: Verified Comment #4 on issue 1672 by percival.music.ca: patch Allows LilyPond to ignore certain note-heads in a stem http://code.google.com/p/lilypond/issues/detail?id=1672 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1672 in lilypond: patch Allows LilyPond to ignore certain note-heads in a stem
Updates: Status: Invalid Labels: -Patch-review Comment #3 on issue 1672 by percival.music.ca: patch Allows LilyPond to ignore certain note-heads in a stem http://code.google.com/p/lilypond/issues/detail?id=1672 this patch was withdrawn by Mike. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2.14 linux download page error
On Tue, Jun 07, 2011 at 07:41:57AM +1000, Nick Payne wrote: > The "compiling a file" example on the right-hand side of the > download page (http://lilypond.org/unix.html) has a version number > in the sample ly file of 2.15.0. Should be 2.14.0. Please send such messages to bug-lilypond. Bug Squad: when you add it to the tracker, please add a warning from me that fixing this includes 2-3 "gotchas". Each "gotcha" could easily waste an hour of time, or could be resolved by sending a 2-sentence email to me. Anybody working on this should contact me if they get stuck for longer than 10 minutes on any step. Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: source download link broken
On Mon, Jun 06, 2011 at 02:40:49PM -0700, Josiah Boothby wrote: > The download link on the source download page[1] refers to the v2.12 > directory, so it points to the wrong place[2]. Easily worked around by > way of manual navigation, but the link itself is broken. Thanks, fixed in git and should appear online within an hour. Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1658 in lilypond: Doc: need documentation of \cueClef and \cueDuringWithClef
Comment #5 on issue 1658 by percival.music.ca: Doc: need documentation of \cueClef and \cueDuringWithClef http://code.google.com/p/lilypond/issues/detail?id=1658 Thanks, Reinhold. For clarity: nothing input/regression/ is considered to be part of the documentation, so James still needs to do something. Copying the contents of two files into Documentation/snippets/new/ is probably the cheapest&easiest method -- but that isn't a specific recommendation. I'm not familiar enough with this material, nor the Notation section, to judge. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: CHANGES -> 2.14 instead of 2.13
On 7 June 2011 09:37, Xavier Scheuer wrote: > Congratulations for the release of 2.14! > > CHANGES is showing "New features in 2.13 since 2.12". > Shoudln't it be updated to ""New features in 2.14" etc. ? I forgot the link: http://lilypond.org/doc/v2.14/Documentation/changes/index.html Cheers, Xavier -- Xavier Scheuer ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Website doc search still using 2.12
If we use the search box in the bottom of the left panel in the Notation Reference, it makes a google search with site:lilypond.org +v2.12 mysearch Should it be changed to site:lilypond.org +v2.14 mysearch since 2.14 is now the latest stable version? Cheers, Xavier -- Xavier Scheuer ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
CHANGES -> 2.14 instead of 2.13
Congratulations for the release of 2.14! CHANGES is showing "New features in 2.13 since 2.12". Shoudln't it be updated to ""New features in 2.14" etc. ? Cheers, Xavier -- Xavier Scheuer ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
