Re: XML to .ly and Lilypond, again

Whoops. I had responded before reading the new digests, apologies; seems David has discovered the root of the issue, thank you very much! Cheers, Leszek. On 16 May 2017 at 09:47, Leszek Wroński wrote: > Hi Robert, > > thanks! I tried your file and I get similar messages: > >

Re: XML to .ly and Lilypond, again

Hi Robert, thanks! I tried your file and I get similar messages: - musicxml2ly: Reading MusicXML from Kyrie_copy.xml ... musicxml2ly: Converting to LilyPond expressions... () musicxml2ly: Output to `Kyrie_copy.ly' Traceback (most recent call last): File

Re: XML to .ly and Lilypond, again

On Fri 12 May 2017 at 11:59:05 (+0100), Phil Holmes wrote: > - Original Message - From: "Urs Liska" <u...@openlilylib.org> > To: <lilypond-user@gnu.org>; <bug-lilyp...@gnu.org> > Sent: Friday, May 12, 2017 11:00 AM > Subject: Re: XML to .ly and Li

Re: XML to .ly and Lilypond, again

On Sun 14 May 2017 at 08:33:26 (+0200), zs.has...@gmx.de wrote: > >On Fri 12 May 2017 at 12:03:36 (+0200), David Kastrup wrote: He wrote something else. But I wrote… > >My guess is that the wrong encoding comes from "original" strings > >being passed from the input to the output as opposed to

Re: XML to .ly and Lilypond, again, with a fix

On Sun 14 May 2017 at 15:35:51 (+0100), Phil Holmes wrote: > - Original Message - From: "Urs Liska" <u...@openlilylib.org> > To: <lilypond-user@gnu.org> > Sent: Sunday, May 14, 2017 3:06 PM > Subject: Re: XML to .ly and Lilypond, again > >Am

Re: XML to .ly and Lilypond, again

Hi Leszek, Thanks for your reaction to my post. Interesting, yes, but of little help to you. We could do a little test. What happens if you use the xlm-file that can be downloaded from this link here? https://dl.dropboxusercontent.com/u/512573/FileChute/Kyrie_copy.zip Best regards, Robert

Re: XML to .ly and Lilypond, again

On Sun, 14 May 2017 16:06:47 +0200, Urs Liska wrote: > But can that be? Shouldn't MusicXML allow arbitrary regular Unicode > characters? Yes, but the file should be encoded using a single encoding. In this case, some parts of the file are UTF-8 encoded while other parts

Re: XML to .ly and Lilypond, again

- Original Message - From: "Urs Liska" <u...@openlilylib.org> To: <lilypond-user@gnu.org> Sent: Sunday, May 14, 2017 3:06 PM Subject: Re: XML to .ly and Lilypond, again Am 14.05.2017 um 16:03 schrieb Phil Holmes: I've just confirmed Ian Ring's suggestion -

Re: XML to .ly and Lilypond, again

Am 14.05.2017 um 16:03 schrieb Phil Holmes: > I've just confirmed Ian Ring's suggestion - removing the copyright > symbol allows the conversion to continue, but results in text with > spurious null characters. But can that be? Shouldn't MusicXML allow arbitrary regular Unicode characters? Urs

Re: XML to .ly and Lilypond, again

- Original Message - From: "Phil Holmes" <m...@philholmes.net> To: "Leszek Wronski" <elw...@gmail.com>; <lilypond-user@gnu.org> Sent: Sunday, May 14, 2017 2:31 PM Subject: Re: XML to .ly and Lilypond, again - Original Message - Fr

Re: XML to .ly and Lilypond, again

- Original Message - From: "Leszek Wronski" <elw...@gmail.com> To: <lilypond-user@gnu.org> Sent: Friday, May 12, 2017 12:54 PM Subject: Re: XML to .ly and Lilypond, again Dear Phil, I read through the 2 pages of comments at the link you provided. Is the ultim

Re: XML to .ly and Lilypond, again

Hi David, Ref.: "What's the role of TeXShop? What process did it carry out? " TeXShop, by means of its LilyPond Engine, processed the file containing the code copied from Frescobaldi. I processed the file with two LilyPond versions, 2.18.2 and 2.19.58.1, and as far I could see the results were

Re: XML to .ly and Lilypond, again

On Sun 14 May 2017 at 12:42:03 (+0200), Robert Blackstone wrote: > Hi Leszek, > > Out of curiosity I downloaded and processed the Kyrie.xml, from the link you > attached to your post of 12-05-17. > I was curious in particular because I mostly use the same procedure for > engraving with

Re: XML to .ly and Lilypond, again

Hi Leszek, Out of curiosity I downloaded and processed the Kyrie.xml, from the link you attached to your post of 12-05-17. I was curious in particular because I mostly use the same procedure for engraving with LilyPond as you do, starting with Finale, except that I'm on a Mac (OSX 10.9.5

Re: XML to .ly and Lilypond, again

>On Fri 12 May 2017 at 12:03:36 (+0200), David Kastrup wrote: > >My guess is that the wrong encoding comes from "original" strings >being passed from the input to the output as opposed to all the >normal strings that are generated by the conversion program. These >original strings would carry

Re: XML to .ly and Lilypond, again

On Fri 12 May 2017 at 12:03:36 (+0200), David Kastrup wrote: > 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

Re: XML to .ly and Lilypond, again

- Original Message - From: "Leszek Wronski" <elw...@gmail.com> To: <lilypond-user@gnu.org> Sent: Friday, May 12, 2017 12:54 PM Subject: Re: XML to .ly and Lilypond, again Dear Phil, I read through the 2 pages of comments at the link you provided. Is the ultim

Re: XML to .ly and Lilypond, again

Dear Phil, I read through the 2 pages of comments at the link you provided. Is the ultimate suggestion the one in your last comment, that is, "I believe this patch requires Python 2.7, and we ship 2.4. As a result, windows users can no longer use musicxml2ly." ? If so, I should just mention that

Re: XML to .ly and Lilypond, again

Dear Guys, first, thank you very much for the replies! Second, for a little bit of detective work. I have not updated my Finale in years, so if it produced correct XML files in the past, it should do the same now (I always write using a similar really basic setup, since actual editing is to be

Re: XML to .ly and Lilypond, again

- Original Message - From: "Urs Liska" <u...@openlilylib.org> To: <lilypond-user@gnu.org>; <bug-lilyp...@gnu.org> 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 Lesze

Re: XML to .ly and Lilypond, again

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

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

Re: XML to .ly and Lilypond, again

Guys, I was a bit too quick with 'It all looks OK in Hex". When I opend the .ly in Emacs I saw "^@" characters after all letters ("t^@i^@m^@e^@" etc). I removed all of them. This almost did the trick and finally the file was compilable after a few minor edits. So it seems that the 'EOF' issue is

Re: XML to .ly and Lilypond, again

On Fri, 12 May 2017 11:14:53 +0200, Leszek Wroński wrote: > I looked at the file using > a Hex viewer and I see nothing wrong with it. The strings like "Finale ..." and some other parts of the file are multy-byte (UTF-16) encoded while the rest of the file is single-byte, so

Re: XML to .ly and Lilypond, again

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

XML to .ly and Lilypond, again

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