From 8cea88f78f766476cbb82cb7e53b1f6223159cb2 Mon Sep 17 00:00:00 2001 From: Urs Liska Date: Mon, 6 Mar 2017 23:05:31 +0100 Subject: [PATCH 1/1] 5085: Web-GSoC: Small touches to MusicXML project description --- Documentation/web/community.itexi | 36 +++++++++++++++---------------- 1 file changed, 17 insertions(+), 19 deletions(-) diff --git a/Documentation/web/community.itexi b/Documentation/web/community.itexi index 80374ac666..7d27daf66e 100644 --- a/Documentation/web/community.itexi +++ b/Documentation/web/community.itexi @@ -1099,32 +1099,30 @@ Integration (can be learned during the bonding period) Improving MusicXML import and export functions: -File interchange between LilyPond and other applications using MusicXML is still -a difficult matter. To import MusicXML it has to be converted manually by -mysicxml2ly. Export is only available as midi file or as a rudimentary feature -inside Frescobaldi. In order to provide natural interchange between LilyPond -and MusicXML-based applications there's need of an import functionality -and an export backend. - -Importing XML shall provide file, line and column to add origin-attributes to -generated objects. That way point and click can be made available in Frescobaldi -or other supported IDEs. - -Exporting XML shall be realized with an exporter class like the Midi export. -This may be based on the work already done in +File interchange between LilyPond and other applications using MusicXML +is still a difficult matter. To import MusicXML it has to be converted +manually by the @code{musicxml2ly} script. Export @emph{to} MusicXML is +only available as a rudimentary feature inside Frescobaldi. In order to +provide natural interchange between LilyPond and MusicXML based +applications there's the need of actual import functionality and a +dedicated export backend. + +Importing XML shall provide file, line and column to add origin +attributes to generated objects. That way point and click can be +made available in Frescobaldi or other supported IDEs. + +Exporting XML shall be realized with an exporter class like the MIDI +export. This may be based on the work already done in @uref{https://github.com/DavidGarfinkle/Lilypond_MusicXMLexport, GSoC 2015} -by David Garfinkle. It should be checked, if it is suitable to use another -XML-library than the one provided by guile-2, so that this feature is -available in current LilyPond - based on guile-1.8. - +by David Garfinkle. It should be checked if it is possible to use +another XML library than the one provided by guile-2 in order to have +this feature available in current LilyPond (which is based on guile-1.8). @strong{Difficulty:} medium @strong{Requirements:} MusicXML, Python, Scheme, basic LilyPond knowledge @strong{Recommended:} Familiarity with other scorewriters (for cross-testing) @strong{Mentor:} Jan-Peter Voigt - - @divEnd @divClass{column-center-middle-color2} -- 2.39.2