Re: Issue 811 in lilypond: PDF conversion fails on OSX PPC

On Fri, Jul 17, 2009 at 9:32 PM, Graham Percival wrote: > On Fri, Jul 17, 2009 at 10:45:11PM +, codesite-nore...@google.com wrote: >> Graham, can you make sure darwin-ppc::ghostscript and >> darwin-x86::ghostscript get >> completely clean rebuilds for 2.13.4?  That might solve the problem. > >

Re: Issue 811 in lilypond: PDF conversion fails on OSX PPC

On Fri, Jul 17, 2009 at 10:45:11PM +, codesite-nore...@google.com wrote: > Graham, can you make sure darwin-ppc::ghostscript and > darwin-x86::ghostscript get > completely clean rebuilds for 2.13.4? That might solve the problem. rm -rf target/darwin-x86 rm -rf target/darwin-ppc will do

Issue 811 in lilypond: PDF conversion fails on OSX PPC

Updates: Cc: gpermus Comment #3 on issue 811 by pnorcks: PDF conversion fails on OSX PPC http://code.google.com/p/lilypond/issues/detail?id=811 How very odd. :-( The only difference between the two Darwin tarballs is that ppc has a "gtester" binary, but x86 does not. But "gtester" d

Issue 811 in lilypond: PDF conversion fails on OSX PPC

Comment #2 on issue 811 by v.villenave: PDF conversion fails on OSX PPC http://code.google.com/p/lilypond/issues/detail?id=811 Yes indeed: << gs -dSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite -sOutputFile="./Un

Issue 811 in lilypond: PDF conversion fails on OSX PPC

Comment #1 on issue 811 by pnorcks: PDF conversion fails on OSX PPC http://code.google.com/p/lilypond/issues/detail?id=811 The Ghostscript error messages are a lot more clear when you run lilypond --verbose Then we will know what "(256)" means, hopefully. -- You received this message becaus

Issue 569 in lilypond: Consistency in property names: beam-thickness

Updates: Owner: Carl.D.Sorensen Comment #3 on issue 569 by Carl.D.Sorensen: Consistency in property names: beam-thickness http://code.google.com/p/lilypond/issues/detail?id=569 (No comment was entered for this change.) -- You received this message because you are listed in the owner

Issue 569 in lilypond: Consistency in property names: beam-thickness

Updates: Status: Started Comment #2 on issue 569 by Carl.D.Sorensen: Consistency in property names: beam-thickness http://code.google.com/p/lilypond/issues/detail?id=569 Assigned to Frederic Bron as a Frog task. -- You received this message because you are listed in the owner or CC f

Issue 783 in lilypond: release list for 2.14

Comment #5 on issue 783 by v.villenave: release list for 2.14 http://code.google.com/p/lilypond/issues/detail?id=783 The new text cresc feature is now known as issue 817. By the way, I am in no place to decide what qualifies as a release_blocker, so I'll leave it up to you guys. I will not o

Issue 817 in lilypond: Enhancement: new syntax for more flexible cresc/dim spanners

Status: Started Owner: v.villenave CC: reinhold.kainhofer, n.puttock, pnorcks Labels: Type-Enhancement Priority-Medium New issue 817 by v.villenave: Enhancement: new syntax for more flexible cresc/dim spanners http://code.google.com/p/lilypond/issues/detail?id=817 Currently, dynamics have t

Issue 783 in lilypond: release list for 2.14

Comment #4 on issue 783 by v.villenave: release list for 2.14 http://code.google.com/p/lilypond/issues/detail?id=783 The AJAX thingy is now known as issue 815. Everybody: feel free to send separate requests to bug-lilypond so I can open individual issues as Han-Wen suggested. -- You receiv

Issue 816 in lilypond: Accidentals should use the normal fontsize in figured bass

Status: Started Owner: v.villenave CC: reinhold.kainhofer Labels: Type-Enhancement Priority-Low Engraving-nitpick New issue 816 by v.villenave: Accidentals should use the normal fontsize in figured bass http://code.google.com/p/lilypond/issues/detail?id=816 The way figured bass is printed now

Issue 815 in lilypond: Enhancement: AJAX-powered search auto-completion for the online documentation

Status: Started Owner: v.villenave CC: reinhold.kainhofer Labels: Type-Documentation Priority-Medium Usability New issue 815 by v.villenave: Enhancement: AJAX-powered search auto-completion for the online documentation http://code.google.com/p/lilypond/issues/detail?id=815 This nice feature c

Issue 508 in lilypond: request: support 128 durations

Updates: Status: Verified Labels: fixed_2_11_66 Comment #10 on issue 508 by v.villenave: request: support 128 durations http://code.google.com/p/lilypond/issues/detail?id=508 OK, it definitely does work. Sorry for the noise. -- You received this message because you are listed in

Re: Mac OS X LilyPond & Terminal install problems.

On Thu, Jul 16, 2009 at 12:38:35PM +0200, Valentin Villenave wrote: > 2009/7/16 Graham Percival : > > If you want more info, read the -devel archives.  Particularly > > emails with "release" or "osx" or "gui" in the title. > > I have, which is why I'm asking. Huh, I can't find the email I thought

Issue 814 in lilypond: warning-as-error should be enabled when compiling the regtests

Status: Accepted Owner: v.villenave CC: pnorcks, john.mandereau, n.puttock Labels: Type-Enhancement Priority-Medium Maintainability New issue 814 by v.villenave: warning-as-error should be enabled when compiling the regtests http://code.google.com/p/lilypond/issues/detail?id=814 The new -dw

Re: "Stress test" for the regression tests

2009/7/16 Patrick McCarty : > Step 3.) might be a few years away, but IMO, this should be on the > tracker so it is not lost. I hear you. http://code.google.com/p/lilypond/issues/detail?id=814 Regards, Valentin ___ bug-lilypond mailing list bug-lilyp

Re: error with eps backend

2009/7/17 Patrick McCarty : > Neil has a patch for this: http://codereview.appspot.com/7262/show > > It will be fixed eventually.  :-) There's no way I'm gonna let this one go. http://code.google.com/p/lilypond/issues/detail?id=813 (marked as "started", will be closed as soon as the patch gets pus

Issue 813 in lilypond: non-existing intermediate ps files when using the eps backend

Status: Started Owner: v.villenave CC: n.puttock Labels: Type-Defect Priority-Low Warning-nitpick New issue 813 by v.villenave: non-existing intermediate ps files when using the eps backend http://code.google.com/p/lilypond/issues/detail?id=813 When using the eps backend, LilyPond still tries

Issue 812 in lilypond: ./configure detects incorrect set of Century Schoolbook fonts

Status: Accepted Owner: v.villenave Labels: Type-Defect Priority-Low Build New issue 812 by v.villenave: ./configure detects incorrect set of Century Schoolbook fonts http://code.google.com/p/lilypond/issues/detail?id=812 Reported by Patrick McCarty and John Mandereau: " If the ~/.fonts dire

Re: Problem finding correct Century Schoolbook fonts

2009/7/16 Patrick McCarty : > Configure detects incorrect set of Century Schoolbook fonts OK, thank you all. Here you go: http://code.google.com/p/lilypond/issues/detail?id=812 Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.g

Issue 811 in lilypond: PDF conversion fails on OSX PPC

Status: Accepted Owner: v.villenave Labels: Type-Defect Priority-Medium OpSys-OSX New issue 811 by v.villenave: PDF conversion fails on OSX PPC http://code.google.com/p/lilypond/issues/detail?id=811 Either launched from the GUI or from the Terminal, LilyPond 2.13.3 now works fine on both Tiger a

Issue 764 in lilypond: convert-ly does not work in the lilypad for OSX 10.4

Comment #6 on issue 764 by v.villenave: convert-ly does not work in the lilypad for OSX 10.4 http://code.google.com/p/lilypond/issues/detail?id=764 Launched from the GUI, convert-ly 2.13.3 fails on Leopard PPC with the following traceback: convert-ly (GNU LilyPond) 2.13.3 Processing `/U