lilypond-user
[Top][All Lists]
Advanced

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

Re: XML to .ly and Lilypond, again


From: Jan-Peter Voigt
Subject: Re: XML to .ly and Lilypond, again
Date: Fri, 12 May 2017 11:26:44 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0

Dear Leszek,

when I look with hexdump, I see a lot of NUL-bytes inside the file. And it seems to me that the strings are in UTF-16 and the rest in latin-1 or the like. At least it seems like a mixture of encodings.

Jan-Peter

Am 12.05.2017 um 11:14 schrieb Leszek Wroński:
Dear Guys,

I see a similar issue has been discussed recently, so apologies for
bringing it up again, but I want to highlight a different aspect of
it, at least I think I do -- sorry if I'm mistaken. My point is that
the .ly code converted from .xml does not compile simply under
lilypond (I'm using 2.19.48), and not just 'in Frescobaldi'.

Throughout the years my method of working has been the following:
1. Enter music in Finale, on Windows 7, via a MIDI keyboard
2. Export to MusicXML
3. Switch to Ubuntu Linux
3. Convert to .ly
4. Edit in Frescobaldi.

I haven't done the converting in a while; I've been editing some older
files. However, today I realised that my simple method is no longer
working. I arrived at this file:
https://www.dropbox.com/s/cmvbn3z4jsar613/Herr_nun_01.ly?dl=0 which
has at the header the following:

5. \header {
6.    encodingsoftware =
7.    "Finale 2012 for Windows"

(...)

and Lilypond itself, not just Frescobaldi, gives me this:

-----------------------------------
GNU LilyPond 2.19.48
Processing `Herr_nun_01.ly'
Parsing...
Herr_nun_01.ly:7:5: error: EOF found inside string

    "
Herr_nun_01.ly:7:5: error: syntax error, unexpected end of input,
expecting \header

    "
fatal error: failed files: "Herr_nun_01.ly"
-----------------------------------

(Frescobaldi's message is similar.)

Even after removing the header altogether, the error just 'moves down
the file'. I am completely baffled by this. I looked at the file using
a Hex viewer and I see nothing wrong with it. My old files compile
correctly, so it seems something has to be wrong with the new file.

Am I making some stupid mistake? Could anyone offer some advice?

Best regards,

Leszek.

_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user





reply via email to

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