-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