Re: Issue 1913 in lilypond: musicxml2ly: <movement-title> not converted in the presence of a non-empty <work-title>

[lilypond]

Updates:
        Status: Started
        Owner: address@hidden
        Labels: Patch-new

Comment #1 on issue 1913 by address@hidden: musicxml2ly:  
<movement-title> not converted in the presence of a non-empty <work-title>
http://code.google.com/p/lilypond/issues/detail?id=1913

address@hidden via gnu.org to reinhold.kainh., reply,  
lilypond-devel
show details 12:35 PM (2 minutes ago)
Reviewers: Reinhold,

Description:
musicxml2ly: title and subtitle (issue 1913), miscellaneous

musicxml2ly: titles (fixes issue 1913), tagline, conversion-info,
<source>, midi-cmd-line-option, center-column long instrument names

1) if XML: <work-title>bli</work-title> AND <movement-title>bla
</movement-title> --> LilyPond: title = bla subtitle = bli

2) the tagline of a piece engraved by LilyPond should not contain any
information as to the encoding software of the .xml file. The standard
Lilypond-tagline should be used.

3) the conversion info should contain the name of the conversion tool

4) the <source>-element is converted to a custom LilyPond-variable
named "source" in the header. (it is usually used for publishing
information)

5) a command line option for a midi block was added

6) multi-lined instrument names are now typeset in center-columns

7) the <miscellaneous>-element is currently translated into a header-
variable "texidoc" which is important for the documentation. I'd suggest
to call it "miscellaneous" by default and call it "texinfo" when
activated via a command line option. (Not implemented yet)

Please review this at http://codereview.appspot.com/5096050/

Affected files:
 M python/musicexp.py
 M python/musicxml.py
 M scripts/musicxml2ly.py