Re: XML to .ly and Lilypond, again

[Phil Holmes]

- Original Message - 
From: "Urs Liska" 

To: ; 
Sent: Friday, May 12, 2017 11:00 AM
Subject: Re: XML to .ly and Lilypond, again





Am 12.05.2017 um 11:26 schrieb Jan-Peter Voigt:

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.


I think this is exactly what was discussed in the mentioned recent thread.
So it seems this is an issue in musicxml2ly that has recently been
introduced. Does anyone know or can anyone find out when this happened
(by trying musicxml2ly from different LilyPond versions)?

Urs


See https://sourceforge.net/p/testlilyissues/issues/4751/

--
Phil Holmes 



___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: XML to .ly and Lilypond, again

[David Kastrup]

Urs Liska  writes:

> Am 12.05.2017 um 11:26 schrieb Jan-Peter Voigt:
>> 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.
>
> I think this is exactly what was discussed in the mentioned recent thread.
> So it seems this is an issue in musicxml2ly that has recently been
> introduced. Does anyone know or can anyone find out when this happened
> (by trying musicxml2ly from different LilyPond versions)?

My guess would rather be on some auto-encoding/decoding choice by
Python, possibly triggered by badly (or unexpectedly?) encoded material
in the MusicXML file.

-- 
David Kastrup

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: XML to .ly and Lilypond, again

[Urs Liska]

Am 12.05.2017 um 11:26 schrieb Jan-Peter Voigt:
> 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.

I think this is exactly what was discussed in the mentioned recent thread.
So it seems this is an issue in musicxml2ly that has recently been
introduced. Does anyone know or can anyone find out when this happened
(by trying musicxml2ly from different LilyPond versions)?

Urs

>
> 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
>> lilypond-u...@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>>
>
>
> ___
> lilypond-user mailing list
> lilypond-u...@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

-- 
u...@openlilylib.org
https://openlilylib.org
http://lilypondblog.org


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond