Re: Lilypond lobbying?

[Kieren MacMillan]

Hi Urs,

> This might be another push for thinking about a MusicXML backend.

Yes.

> Althought this may seem opposite of lobbying LilyPond

No, to me this *is* part of "lobbying Lilypond": If we had a seamless MusicXML 
import/export process, users could
(a) Choose to input in Finale/Sibelius (due to comfort level), then output in 
Lilypond.
(b) Choose to input in Lilypond, then output in Finale/Sibelius (due to 
publisher's requirements, etc.)

> it still may encourage people to use LilyPond. I think I'd easier take the 
> decision to make the jump and learn LilyPond if I know that I can still be 
> compatible with the Finale/Sibelius world if necessary.

Precisely!

I hereby reiterate my offers of bounty and/or XML and XSLT coding assistance 
for any MusicXML project/effort — while I can't write C++ (at all) or Scheme 
(almost at all), I can write XSLT stylesheets in my sleep.

Cheers,
Kieren.