Double Oops!! The first quote mark is the correct one - omit the one at
the end (though in fact Windows tolerates it, which is how it got in
there unnoticed).
Paul
On 22/09/2019 15:50:55, "Paul Hodges" wrote:
>Oops! Omit the quote mark in the middle of my statement after .py.
>
>Paul
>
>On
Oops! Omit the quote mark in the middle of my statement after .py.
Paul
On 22/09/2019 11:57:06, "Paul Hodges" wrote:
>Thanks very much for this!
>
>I couldn't work out how your suggested changes can be applied in a
>Windows installation, so instead I did the following:
>(1) Installed Python
Thanks very much for this!
I couldn't work out how your suggested changes can be applied in a
Windows installation, so instead I did the following:
(1) Installed Python 2.7.14 in the system (but without adding it to the
path);
(2) Used the following command (assuming default installation paths)
Hi Michael!
b) Is there work on migrationg to Python3?
I don't think so.
Python2 will be phased out by upstream really soon now.
Yes. We know. No problem If we have our own python2 ;-)
Sad to hear that.
If I find time I'll have a look into it.
Porting to Python3 is relatively doable in my
On 7/15/2019 8:59 AM, Michael Kesper wrote:
If I find time I'll have a look into it.
Porting to Python3 is relatively doable in my experience.
A few other people have expressed interest in working on Python
upgrades. Past discussions indicated that the biggest challenges would
be getting GUB
Hi Knut,
On 15.07.19 15:44, Knut Petersen wrote:
> On 15.07.19 09:34, Michael Kesper wrote:
>> b) Is there work on migrationg to Python3?
> I don't think so.
>
>> Python2 will be phased out by upstream really soon now.
>
> Yes. We know. No problem If we have our own python2 ;-)
Sad to hear
On 15.07.19 09:34, Michael Kesper wrote:
Hi all,
On 14.07.19 22:59, Knut Petersen wrote:
Bug 1:
Musicxml2ly is incompatible to the python2 distributed with the installers.
Musicxml2ly needs at least python2 2.7.0, lilypond installers provide python
2.4.5
This leads me to two questions:
a)
Hi all,
On 14.07.19 22:59, Knut Petersen wrote:
> Bug 1:
> Musicxml2ly is incompatible to the python2 distributed with the installers.
> Musicxml2ly needs at least python2 2.7.0, lilypond installers provide python
> 2.4.5
This leads me to two questions:
a) What's the reason for shipping it's
://lilypond.1069038.n5.nabble.com/issues-with-musicxml2ly-td222401.html),
would it be possible to add those to the tracker, perhaps?
Many, many thanks,
Gilberto
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug
Hi Gilberto!
Try if replacing
musicxml ...
with
python2 $(grep -o '"[^$^"]*$me"' `which musicxml2ly` | sed -e 's/"//g' -e
's/$me/musicxml2ly/') ...
Yes, that does seem to fix the issue! The .ly file created by musicxml2ly does not have the encoding and strange character issues and
Hi Knut,
You did not answer the question if you used one of the installers from
lilypond.org or if you compiled lilypond.
My apologies, forgot about that bit. I am not compiling myself, I am
using the installers from lilypond.org.
Try if replacing
musicxml ...
with
python2 $(grep
Hi Gilberto!
I use Linux Mint 18.3, 64-bit, and my LilyPond is version 2.19.82. The default python interpreter in my installation is 2.7.12, which I think is what came with my Linux Mint 18.3 (I believe I've never bothered trying to update it since I do all my Python coding with Python 3). Do
Hi Knut,
Thanks a lot for your reply. I use Linux Mint 18.3, 64-bit, and my
LilyPond is version 2.19.82. The default python interpreter in my
installation is 2.7.12, which I think is what came with my Linux Mint
18.3 (I believe I've never bothered trying to update it since I do all
my Python
Hi Gilberto!
Let me know if I can help with anything else.
Which operating system do you use? 32-bit or 64-bit?
I suspect that you did not compile Lilypond yourself but used one of the
installers. Am I right?
If I'm right: Don't use the python interpreter distributed with lilypond, use
Just a small follow up, I forgot to mention that I my musicxml2ly version is
2.19.82. I am also attaching a .musicxml file generated by MuseScore and the
.ly file generated by musicxml2ly. The .ly file does not compile and has the
hidden characters and strange enconding I mentioned.
test.musicxml
Hello bug-squad,
I ran into three issues when converting a .musicxml file generated with
MuseScore into LilyPond:
1) the .ly file outut by musicxml2ly seems to have a weird encoding and
outputs an error. There are many hidden characters which I had to remove
manually in order to compile
16 matches
Mail list logo
