Replies: 2 comments 5 replies
-
Exactly the same problem exists with |
Beta Was this translation helpful? Give feedback.
2 replies
-
I've tested the snippet below with both MuseScore pre-4.4.0 and Finale 27. <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE score-partwise PUBLIC "-//Recordare//DTD MusicXML 2.0 Partwise//EN"
"http://www.musicxml.org/dtds/partwise.dtd">
<score-partwise version="2.0">
<part-list>
<score-part id="P1">
<part-name>MusicXML Part</part-name>
</score-part>
</part-list>
<part id="P1">
<measure number="1">
<attributes>
<divisions>1</divisions>
</attributes>
<direction>
<direction-type>
<rehearsal enclosure="rectangle">12</rehearsal>
<rehearsal enclosure="rectangle" font-style="italic"> bis</rehearsal>
</direction-type>
</direction>
<note>
<pitch><step>C</step><octave>4</octave></pitch>
<duration>4</duration>
<type>whole</type>
</note>
</measure>
</part>
</score-partwise> |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
For what exactly do I need multiple
<rehearsal>
children in a single<direction-type>
element? Is there an example?I can imagine that this functionality is intended to provide font changes in rehearsal marks:
In case my assumption is correct, however, I don't see any remark in the specification that the
enclosure
attribute should unify its arguments, so to say, preventing the following rendering.Please advise.
Beta Was this translation helpful? Give feedback.
All reactions