[Top][All Lists]

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

Re: [PATCHES]: Converting header and lyrics with musicxml2ly

From: Han-Wen Nienhuys
Subject: Re: [PATCHES]: Converting header and lyrics with musicxml2ly
Date: Sat, 01 Sep 2007 12:10:08 -0300
User-agent: Thunderbird (X11/20070719)

Reinhold Kainhofer escreveu:
> Hi Han-Wen!
> Attached are two more patches, which already address some of the points you 
> mention.
> -) 2007-09-01_0008-MusicXML-Conversion-of-various-types-of-spanners-o.patch  
> converts some more spanners from MusicXML to lilypond. In particular, octave 
> shifts, trill spanners, glissando and bends.
> -) 2007-09-01_0009-MusicXML-Convert-all-clefs-escape-in-header-fiel.patch    
> Convert all available clefs to lilypond. Also address the issues by Han-Wen 
> mentioned below. Don't be so strict about quoting in lyrics: Only wrap the 
> lyrics syllables in quotes if necessary (but then also escape " in lyrics and 
> header fields!).
> Am Samstag, 1. September 2007 schrieben Sie:
>> if you intend to work on this more, I could give you write access to the
>> repository.  It would require you to sign up for
> Yes, I'm planning to do some more work on musicxml2ly, at least until it is 
> in 
> a state that it's easier for me to scan a score, export it to MusicXML and 
> run musicxml2ly than to write it from scratch in lilypond.

Cool. You might want to contact Darius Blasband , address@hidden , who has
been asking me for better MusicXML support for some time.  He will also have
good Finale examples. 

>> * In general, git commit messages should have the following form
>>   1-line summary
>>   background - typically the reason why you are doing it, or the
>>   general idea behind it.
> Okay, in KDE we don't have any such requirement

I have actually started using this format for my work at Google too.
The 1-line summary often shows up in compressed views, so it's nice
to have.  The background helps understand why we have that patch.

>> Keep the 80 column limit in mind here. 
> Okay, again, with KDE svn that limit is no issue.

the limit is not an issue technically, it just makes for easier reading.

> almost all clefs are correctly converted from Finale 2007 to lilypond (the 
> only problem I still have is the "None" key, which means that no key should 
> be used. Lilypond does not seems to support this :-((( ).

what does that mean, "no key" - what's the difference between C-major?


Han-Wen Nienhuys - address@hidden -

reply via email to

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