bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [musicxml2ly] breath mark inside beam


From: James
Subject: Re: [musicxml2ly] breath mark inside beam
Date: Sun, 12 Jan 2014 12:29:57 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0

On 12/01/14 07:57, pls wrote:
On 12.01.2014, at 03:52, Andre Soares<address@hidden>  wrote:

>>I'm not top posting.
>Hello!
>I have this example file.xml:
><score-partwise>
>    <part-list>
>        <score-part id="1"/>
>    </part-list>
>    <part id="1">
>        <measure>
>            <note>
>                <pitch>
>                    <step>C</step>
>                    <octave>4</octave>
>                </pitch>
>                <duration>2</duration>
>                <beam>begin</beam>
>            </note>
>            <note>
>                <pitch>
>                    <step>E</step>
>                    <octave>4</octave>
>                </pitch>
>                <duration>2</duration>
>                <beam>end</beam>
>                <notations>
>                    <articulations>
>                        <breath-mark/>
>                    </articulations>
>                </notations>
>            </note>
>        </measure>
>    </part>
></score-partwise>
>
>
>When i run "musicxml2ly file.xml" i got file.ly with something like this:
>% file.ly begin
>\version "2.18.0"
>...
>c2 [ e2 \breathe ]
>...
>% file.ly end
>
>
>Notice that "\breathe" is before "]" causing an error when I run "lilypond
>file.ly":
>teste.ly:14:22: error: syntax error, unexpected EVENT_IDENTIFIER
>    c2 [ e2 \breathe
>                     ] }
>
>Sorry for the long report. It was the tinyest example i could build.
>I'm just willing to help lilypond community, which I love!
Hi Andre,

thanks for the report!  It definitely is a bug.

http://code.google.com/p/lilypond/issues/detail?id=3800

Although I am not sure what the proper title should be - I made an educated guess

'MusicXML beaming information causes LP file compilation errors with some markup scripts'

james



reply via email to

[Prev in Thread] Current Thread [Next in Thread]