>> 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
-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
-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
>
-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
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
> 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 backend from creating
> .tex(i) and .count files:
>
> http://codereview.appspot.com/110107
>
> Okay to apply?
N
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
since I'm currently using lilypond to create lots of small example files for a
larger thesis (written in Word), I'm using the eps backend to create nicely
clipped images. However, instead of one file per example, the eps backend
creates a .tex, a .t
