Re: PNG output not working (Mac OS X Lion)

[Colin Hall]

Hi Raphael,

On Wed, May 23, 2012 at 01:28:33PM +0000, Raphael Frey wrote:
> 
> unfortunately PNG output doesn't work on Mac OS X Lion & LilyPond
> 2.15.38 - here's the Terminal output:
> 
> --
> new-host:~ raphael$ exec /Applications/LilyPond.app/Contents/
> Resources/bin/lilypond --png 
> Desktop/Test.ly 
> GNU LilyPond 2.15.38
> »Desktop/Test.ly« wird verarbeitet
> Analysieren...
> Interpretation der Musik...[8][8]
> Vorverarbeitung der grafischen Elemente...
> Ideale Seitenanzahl wird gefunden...
> Musik wird auf eine Seite angepasst...
> Systeme erstellen...
> Layout nach »Test.ps« ausgeben...
> Konvertierung nach PNG...
> *** Warning: GenericResourceDir doesn't point to a valid resource directory.
>                the -sGenericResourceDir=... option can be used to set this.
> 
> 
> Kompilation erfolgreich beendet
> 
> [Process completed]

I have an update on your bug report.

Firstly, it looks like the warning messages have been present with
Lilypond on Mac OS X since 2010. See the issue tracker below, which is
about chord names, but also has the GenericResourceDir warning:

http://code.google.com/p/lilypond/issues/detail?id=1353

Since your bug report came in another Mac OS X user, Hans Aberg, has
reported the same warning when he uses the --png option but he also
notes that the PNG file is produced. See the link below:

http://lists.gnu.org/archive/html/bug-lilypond/2012-05/msg00207.html

So, could you confirm that you get a PNG file produced on your system?

I have created an issue tracker for the unexpected warning message:

http://code.google.com/p/lilypond/issues/detail?id=2568

> PS: Other question: Why does LilyPond speak German with me although my
> system's language is set to British English (Formats is set to Switzerland
> (German) but this shouldn't affect the language) ...

That must be a bit of a pain. I've created a separate tracker for that
part of your report:

http://code.google.com/p/lilypond/issues/detail?id=2569

The Lilypond project has no maintainer for the Mac OS X port right
now. I hope there will be progress on fixing these issues when we have
a Mac OS X maintainer.

Cheers,
Colin.

-- 

Colin Hall