> the following musicxml file contains a <direction> element, which I
> hoped would be ignored if I run musicxml2ly with the --nd option,
> but it's not. So either this is a bug, or I misunderstand what is
> --nd supposed to do.
The term 'direction' has two meanings, which is slightly confusing, I
admit: Either the `<direction>` MusicXML element or a 'direction' in
LilyPond speak, i.e., whether an object is positioned above or below a
staff (the latter is denoted by the `placement` attribute in
MusicXML). Option `--nd` makes `musicxml2ly` ignore the `placement`
attribute.
> In any case, it would be great to have an option that would
> basically get rid of all <direction> elements; I work a lot with
> musicxml files from cpdl.org, which are often poorly formatted and
> use <direction> for all sorts of stuff unrelated to the music
> itself.
The `<direction>` container covers a large group of musical symbols,
and omitting it completely is far too radical IMHO. You have to be
more specific which subtypes (i.e., which `<direction-type>` elements)
should be ignored, and whether really a large group of files from
cpdl.org is affected by the problem you describe.
BTW, filtering out all `<direction> ... </direction>` blocks can be
easily done with a script containing a few lines of Perl or Python
code.
Werner
