|
From: | Hans Aikema |
Subject: | Re: musescore lands sponsoring? |
Date: | Wed, 30 May 2012 00:02:23 +0200 |
User-agent: | Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 |
On 29-5-2012 23:16, Nils wrote:
On Tue, 29 May 2012 10:15:31 +0200 Marc Weber<address@hidden> wrote:Musecore fails to render some specific cases when printing - but exporting to lilypond seems to work in all (little) cases I tried. Thus for simple cases I like that combination: musescore for typing and lilypond for rendering.AFAIK musescore dropped Lilypond export support because of a lack of interest and in favour of musicXML (whatever that means, I read it somewhere on the musescore twitter account or something like this). It may still work, but we can expect it to break a little more with each Lilypond release. Nils _______________________________________________ lilypond-user mailing list address@hidden https://lists.gnu.org/mailman/listinfo/lilypond-user .
Nils,Isn't it the 'dropped lilypond import', which apparently has been dropped the second time recently?
http://musescore.org/en/node/14273AFAIK they intend to keep .ly export, but refuse to do .ly import unless new developers want to pick up the task of fixing and maintaining the importer code as import would need to be able to handle the various changes in the lilypond source format gracefully. The export is easier to maintain as they just write the \version in the .ly file and leave it up to the user to run convert-ly and modify anything that convert-ly can't handle itself when using a more recent version of Lilypond.
regards, Hans
[Prev in Thread] | Current Thread | [Next in Thread] |