[Top][All Lists]

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

Re: musicxml2ly was re abc2ly

From: Urs Liska
Subject: Re: musicxml2ly was re abc2ly
Date: Mon, 10 Dec 2018 13:27:13 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1

Am 10.12.18 um 13:22 schrieb Andrew Bernard:
Using musicxml2ly with 2.19.82 on a file converted from ABC with the current downloadbale versionof abc2xml, I get a badly messed up header block, which throws errors in lilypond. Here's an example of a tune converted from, perfectly good ABC notation:

\header {
    source =
    encoder =  "address@hidden@address@hidden@address@hidden@address@hidden@ address@hidden@address@hidden@address@hidden@address@hidden@ address@hidden@address@hidden@" ^@
    encodingdate =  "address@hidden@address@hidden@address@hidden@address@hidden@address@hidden@0^@" ^@
    title =  "address@hidden@address@hidden@address@hidden@address@hidden@ address@hidden@address@hidden@,^@ address@hidden@address@hidden@" ^@

[You can see this effect in vi.]

On Debian 9.

Has anybody else encountered this problem?

Yes, this was discussed a few times recently and seems to be caused by an encoding issue with the ancient Python version shipped with LilyPond/musicxml2ly (one of your all-time favourites ;-/ )



lilypond-user mailing list

reply via email to

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