2009/4/30 Werner LEMBERG :
> Interestingly,
>
> lilypond -dbackend=eps lily-7d242e8d.ly
>
> works just fine.
Looks like you were trying to run the snippet with the lilypond-book
preamble included.
You should get the following error message,
The PostScript backend does not support the
system-by
On Wed, Apr 29, 2009 at 04:53:55PM +0200, Reinhold Kainhofer wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Mittwoch, 29. April 2009 15:57:18 Valentin Villenave wrote:
> > 2009/4/29 Graham Percival :
> >
> > 2009/4/29 Graham Percival :
> > > Yes and no. It would be a great strate
On Wed, Apr 29, 2009 at 05:34:10PM +0200, John Mandereau wrote:
> Graham Percival a écrit :
>> I imagine that almost every convert-ly rule would benefit from
>> "match this command, and only this command" rules, so this could
>> save typing. And, more to the point, confusion amongst
>> non-regex-s
[git from today]
Running
lilypond lily-7d242e8d.ly
makes lilypond crash. Below is the full backtrace (I configured with
--disable-optimisation, BTW); not very informative, but...
valgrind gives the following:
Invalid read of size 4
at 0x80519A6: ly_car(scm_unused_struct*) (lily-guile.h
> A quick fix is to handle those two files specially, explicitly
> activating font embedding while lilypond processes the files.
An alternative is that lilypond itself forces embedding of the whole
font if it detects that the font doesn't provide glyph names.
On the other hand, it would be *very*
Folks,
the files
lily-50e2bfee.ly
lily-7d242e8d.ly
fail to be properly built during `make doc'. Using gs 8.64, I get
messages like
Substituting .notdef for glyphIndex11C in the font IPAGothic
while converting the EPS. Older gs versions like 8.62 abort with an
error, BTW. Reason is t
