On 12.01.2014, at 18:07, David Kastrup <d...@gnu.org> wrote: > pls <p.l.schm...@gmx.de> writes: > >> Hm, it's rather a conversion error of expressive marks in general in >> combination with manual beaming (see file attached). >> musicxml2ly places breath marks, dynamics, fermatas, etc. _within_ >> manual beam brackets instead of _after_ the right square bracket. > > Most of that is totally ok. > >> Interestingly LilyPond generates a warning during compilation even >> when expression marks are placed after the closing square bracket. > > Shouldn't. The key thing to note is that a closing square bracket is > just another expressive mark to the parser. A breath mark, however, is > _not_ an expressive mark but a music event of its own. No expressive > marks may be placed behind it, including closing square brackets. Thanks! This explains the fatal error for breath marks within square brackets. As far as other marks (e.g. dynamics and fermatas) are concerned I have to correct myself: they don't cause fatal errors during compilation – whether they are placed inside or outside square brackets. But they generate a warning in either case. So the musicxml2ly issue at stake can be narrowed down to the fact that musicxml2ly should not place breath marks inside square brackets.
IMO it should be mentioned somewhere in the NR that no expressive marks may be placed behind breath marks – perhaps under 'Known issues and warnings' either in subsection 1.3.2 or 1.2.4. > > -- > David Kastrup > > > _______________________________________________ > bug-lilypond mailing list > bug-lilypond@gnu.org > https://lists.gnu.org/mailman/listinfo/bug-lilypond _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
