bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Issue 504 in lilypond: lilypond broken on osx 10.5 x86


From: codesite-noreply
Subject: Issue 504 in lilypond: lilypond broken on osx 10.5 x86
Date: Sun, 30 Dec 2007 09:36:27 -0800

Issue 504: lilypond broken on osx 10.5 x86
http://code.google.com/p/lilypond/issues/detail?id=504

Comment #31 by paconet.org:
LP works in Leopard thanks to iPatcher.

The following is from a Mac user (i'm not one):

iPatcher is a piece of software that seems to enable many programs to
work provided
that they worked on Tiger but not in Leopard.

One has to rename (or drag and drop? i'm not sure) the iPatcher program
to (on?) the
name of the file you want to 'repair'. This method works for LilyPond,
partially. The
LilyPond app now shows a working menu and you can save and process
documents, only it
is not possible to open existing files. At program start, a "No
document could be
created." message is issued and (obviously) no document is created.

The symptoms when trying to open an existing document seem to be an
extension- or
file-type- related problem, with the following message:

LilyPond[547:10b] The LilyPond source type doesn't map to any NSDocumentClass.

One more note: the iPatcher program has to be dragged from the Desktop
(it doesn't
work if it lives in another path) and has to be dragged over a file
from the list
that appears right-clicking on the app, choosing "show package
contents", then
/Contents/Mac OS.

I'm sorry because this all is a forward from another user, in the hope
it's of any value.

I don't know anything of this iPatcher program or how it works, I don't
even know if
it is free software or where it can be downloaded from.

Thanks goes to Francisco CaƱizares for his help.



--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings




reply via email to

[Prev in Thread] Current Thread [Next in Thread]