Re: [PATCH] option to prevent EPS backend from creating .tex/.texi/.count files

Werner LEMBERG wrote: Nice idea. While you are at it, please investigate why there are still clipping problems during the EPS->PNG conversion. [...] As a possible solution, I can imagine that we add an intermediate step to convert the fonts in an EPS file into PS paths, for example, by using th

Re: funky build errors

On 2009-08-28, Werner LEMBERG wrote: > > I assume that "needed" and "unneeded" aren't actually > > contradictions... or maybe they are, and that's why the internal > > error is printed. > > They are contradictions, thus the internal error. It's a rounding > issue in FontForge. > > > Executable

Re: What's the deal with info documentation images?

Graham Percival writes: > Let me be clear. > - are the info docs not finished? yes. > - are the pdf, html, etc. not finished? yes. > - did I completely underestimate the pain in doing ANYTHING with > the lilypond build process? yes. > - would I have completely changed almost everybody about

Re: [PATCH] Move ambitus print callback to scheme

Le 29 août 09 à 06:56, David Kastrup a écrit : Carl Sorensen writes: On Aug 28, 2009, at 1:16 PM, "Nicolas Sceaux" wrote: According to R5RS, it is an error to modify a literal list. If a function returns '(), the caller won't be allowed to apply a modifying function on the result (eg. a

Re: [PATCH] option to prevent EPS backend from creating .tex/.texi/.count files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Samstag, 29. August 2009 03:44:04 schrieb Reinhold Kainhofer: > Here is a patch that introduces a command line option aux-files, which can > be used (-daux-files=#f, -dno-aux-files or #(ly:set-option 'no-aux-files)) > to prevent lilypond's eps backe

Re: [PATCH] option to prevent EPS backend from creating .tex/.texi/.count files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Samstag, 29. August 2009 06:37:40 schrieb Werner LEMBERG: > While you are at it, please investigate why there are > still clipping problems during the EPS->PNG conversion. For an > example, look at the snappizzicato example image in the notation >

Re: Creating books with Scheme

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Montag, 17. August 2009 12:05:23 schrieb Nicolas Sceaux: > Le 17 août 09 à 09:23, Nicolas Sceaux a écrit : > > If you look at the definition of `bookpart-score-handler' in my > > file, you see that the book-part argument is not used. Instead, > > al

PATCH for getting output-suffix to work (Trackers 714 and 404)

Apologies for not putting this one on rietveld, but I couldn't get the Create Issue form to accept the patch or work out what the exact set of options and parameters was for the upload.py python script. So I've fallen back to sending it to the list direct. If it looks OK, could someone please

Re: PATCH for getting output-suffix to work (Trackers 714 and 404)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Samstag, 29. August 2009 15:06:44 schrieb Ian Hulin: > Apologies for not putting this one on rietveld, but I couldn't get the > Create Issue form to accept the patch or work out what the exact set of > options and parameters was for the upload.py py

Re: [PATCH] option to prevent EPS backend from creating .tex/.texi/.count files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Samstag, 29. August 2009 13:10:20 schrieb Reinhold Kainhofer: > Am Samstag, 29. August 2009 06:37:40 schrieb Werner LEMBERG: > > While you are at it, please investigate why there are > > still clipping problems during the EPS->PNG conversion. For a

Re: Creating books with Scheme

Le 29 août 09 à 14:28, Reinhold Kainhofer a écrit : -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Montag, 17. August 2009 12:05:23 schrieb Nicolas Sceaux: Le 17 août 09 à 09:23, Nicolas Sceaux a écrit : If you look at the definition of `bookpart-score-handler' in my file, you see that the

Re: PATCH for getting output-suffix to work (Trackers 714 and 404)

Besten Dank, Reinhold, Patch is now available for review on rietveld http://codereview.appspot.com/110111 Cheers, Ian Hulin ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: [PATCH] Move ambitus print callback to scheme

On 8/28/09 10:56 PM, "David Kastrup" wrote: > Carl Sorensen writes: > >> On Aug 28, 2009, at 1:16 PM, "Nicolas Sceaux" >> wrote: >> >>> >>> According to R5RS, it is an error to modify a literal list. >>> If a function returns '(), the caller won't be allowed to >>> apply a modifying funct

Re: Implement framework for post-fix text (de)cresc spanners

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Sonntag, 23. August 2009 19:57:26 schrieb Reinhold Kainhofer: > So,for now I would simply apply that patch so that the properties get > interpreted, but don't add a new command, which will be changed in the > next version again. Anyone who whats to

Re: Use our own ~s ly:format placeholder, since guile is broken with wide chars

Am Samstag, 22. August 2009 02:07:05 schrieb Reinhold Kainhofer: > Am Samstag, 22. August 2009 00:59:33 schrieb joenee...@gmail.com: > > http://codereview.appspot.com/109070/diff/1/2 > > File lily/general-scheme.cc (right): > > > > http://codereview.appspot.com/109070/diff/1/2#newcode437 > > Line 4

Parser variables, properties and contexts, rooky developer question.

Hi all, I've been grubbing around, grepping my git repository and I need a bit of steering from some of you who've been around the lilypond source longer than me. I'm trying to design a solution to the original request for tracker 714, which asked to be able to specify an alternate output fil

[PATCH] Re: Creating books with Scheme

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Samstag, 29. August 2009 18:09:48 schrieb Nicolas Sceaux: > After playing for a while with handlers, it seems that properly mixing > programmaticaly-generated scores and explicit scores requires some > tweaks in the parser. The hacks exposed earlier

Re: [PATCH] Re: Creating books with Scheme

On 8/29/09 7:01 PM, "Reinhold Kainhofer" wrote: > > You mean something like this patch: >http://codereview.appspot.com/112044 LGTM. Just a question. In your regression test, you first define (add-one-score #f), then you set! it to a lambda function. Is that solely so that you can hav

Re: Fix base attachments for slurs at linebreaks

On Sun, Aug 23, 2009 at 10:23 AM, wrote: > > http://codereview.appspot.com/109071/diff/39/46 > File lily/phrasing-slur-engraver.cc (right): > > http://codereview.appspot.com/109071/diff/39/46#newcode147 > Line 147: if (!g->internal_has_interface (ly_symbol2scm > ("span-bar-interface"))) > this wil

Re: [PATCH] Move ambitus print callback to scheme

Carl Sorensen writes: > On 8/28/09 10:56 PM, "David Kastrup" wrote: > >> Carl Sorensen writes: >> >>> On Aug 28, 2009, at 1:16 PM, "Nicolas Sceaux" >>> wrote: >>> According to R5RS, it is an error to modify a literal list. If a function returns '(), the caller won't be allowe

Re: funky build errors

> Hmm. I've seen these errors for a long time now (maybe a year and a > half), and I'm always using the latest fontforge tarball. > > Testing CVS, I get similar errors, first appearing with feta11: Interesting. I haven't seen them since a long time. Please report this to the FontForge list. H

Re: [PATCH] option to prevent EPS backend from creating .tex/.texi/.count files

>> While you are at it, please investigate why there are still >> clipping problems during the EPS->PNG conversion. For an example, >> look at the snappizzicato example image in the notation reference. > > The bounding box of the generated eps files is simply obtained from > the scencil extents

Re: funky build errors

> Here are my configuration settings for FontForge on a i586 GNU/Linux > box: [...] > > --enable-double IIRC, this option is the very one which makes the problems disappear. Hmm. Perhaps it's better to write to the various distribution packagers, urging them to compile FontForge wi