[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: XML to .ly and Lilypond, again
From: |
David Wright |
Subject: |
Re: XML to .ly and Lilypond, again |
Date: |
Mon, 15 May 2017 11:40:00 -0500 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Sun 14 May 2017 at 08:33:26 (+0200), address@hidden 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 all the
> >normal strings that are generated by the conversion program. These
> >original strings would carry their encoding with them.
> If you are meaning finale is producing the wrong xml, I can tell you
> Sibelius, musescore and capella also have this problem.
No, they all should have the problem as they all write correct
Unicode XML files. The fault was in the python program,
because an enhancement was made before the version was new
enough to handle it corrctly.
Cheers,
David.
- Re: XML to .ly and Lilypond, again, (continued)
- Re: XML to .ly and Lilypond, again, Leszek Wroński, 2017/05/12
- Re: XML to .ly and Lilypond, again, Phil Holmes, 2017/05/12
- Re: XML to .ly and Lilypond, again, Phil Holmes, 2017/05/14
- Re: XML to .ly and Lilypond, again, Phil Holmes, 2017/05/14
- Re: XML to .ly and Lilypond, again, Urs Liska, 2017/05/14
- Re: XML to .ly and Lilypond, again, Phil Holmes, 2017/05/14
- Re: XML to .ly and Lilypond, again, with a fix, David Wright, 2017/05/15
- Re: XML to .ly and Lilypond, again, Johan Vromans, 2017/05/14
Re: XML to .ly and Lilypond, again, zs.hassia, 2017/05/14
- Re: XML to .ly and Lilypond, again,
David Wright <=