Re: Completely separating notation from output logic

[Michael Ellis]

Thanks Graham, I did use python to generate the first set of files
and, being fairly expert with it, python is always my weapon of
choice.  The limitation I see in this case is trying to support a
minimal input format for contributors to use. I was able to make it
work for the Greentree files because MuseScore emitted voice name
variables with a recognizable pattern e.g.  "AAvoiceBA = \relative c''
{" and always ended the music with a closing "}"  on a line by itself,
and so forth.

I don't want to burden contributors with anything that rigid and I
don't want to write a python parser for LilyPond syntax or even adapt
the one that comes with Frescobaldi.  That would feel like hunting
flies with an elephant gun.

Hence the reluctant decision to handle it in Scheme.  I did find a
thread from 2008 between Reinhold K., Han-Wen, and Nicolas S, but they
are operating with pretty high-level knowledge of Lily internals.  It
would be nice to find a well-documented solution that didn't require
combing through the Lily sources.  I'll keep looking.  This can't be
that hard to do, right?

Cheers,
Mike



On Mon, Jan 3, 2011 at 9:44 PM, Graham Percival
<address@hidden> wrote:
> On Mon, Jan 03, 2011 at 05:41:48PM -0500, Michael Ellis wrote:
>> Thanks, Carl.  I probably should have included some background
>> information.  If I had only one piece of music to worry about, I'd do
>> it exactly as you suggest.  Problem is I've got 404 Bach Chorales on
>> the Solfege Resources site and expect to eventually have hundreds or
>> even thousands more from other composers whose work is public domain.
>
> This has been solved a few times.  Look in the mailing list
> archives, and/or look at Reinhold's orchestralily, etc.
>
> Personally, I'd just reinvent the wheel and generate score files
> with python, using some naming scheme for directories and files.
> But I'd do so knowing that this solution was stupidly reinventing
> the wheel.
>
> Cheers,
> - Graham
>