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 thesession.org <http://thesession.org>, perfectly good
ABC notation:
\header {
source =
"^@h^@t^@t^@p^@s^@:^@/^@/^@t^@h^@e^@s^@e^@s^@s^@i^@o^@n^@.^@o^@r^@g^@/^@t^@u^@n^@e^@s^@/^@6^@9^@#^@s^@e^@t^@t^@i^@n^@g^@1^@2^@5^@3^@3^@"
^@
encoder = "^@a^@b^@c^@2^@x^@m^@l^@ ^@v^@e^@r^@s^@i^@o^@n^@
^@2^@1^@8^@" ^@
encodingdate = "^@2^@0^@1^@8^@-^@1^@2^@-^@1^@0^@" ^@
title = "^@M^@o^@r^@n^@i^@n^@g^@ ^@D^@e^@w^@,^@ ^@T^@h^@e^@" ^@
}
[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 ;-/ )
Urs
Andrew
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
