On 01/08/13 at 02:51pm, Glen Larsen wrote:
> On Tue, Jan 8, 2013 at 11:25 AM, Felix Janda <[email protected]> wrote:
>
> > On 01/07/13 at 05:24pm, Glen Larsen wrote:
> > > Very cool, David.
> > > Felix, I knew you'd want something like this made out of that:
> > > Simple python wrapper for this scheme code <
> > https://gist.github.com/4480245>
> >
> > Yeah, I think it still needs some processing. IMO, The header fields
> > should be
> > checked for their validity and the remaining fields written to a
> > preliminary
> > (incomplete) .rdf-file. (They are only required for the .rdf aren't they?)
> >
>
> It is likely this code will supplant the pure-python version that applies
> Mutopia's header rules to the key/value pairs. These are required to build
> the Mutopia tagline, fix up the date-id field, as well as the RDF files.
Ah, the tagline depends on the license. So one should maybe put it into a
different file for later processing? I mean the parsing with lilypond still
takes much longer than the scripts currently used at Mutopia, especially for
big orchestral project. Therefore it would be good to ask lily only once for
the header fields.
I'm not sure what you mean by the "date-id field".
> > Your wrapper looks like a good start.
> >
>
> Thanks. The motivation for it was to make this sort of experimentation with
> lilypond a little easier. For me it is much easier to read scheme code when
> it is formatted; put it in one-long-string and I get lost.
You can also have commands broken in several lines on the command line if you
have them in single quotation marks ("'").
Felix
_______________________________________________
Mutopia-discuss mailing list
[email protected]
http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
