> While I am not an apologist for any operating system, I fear folks
are being far too quick to blame Windows here.
> Like any current operating system concerned with
internationalization, Windows and NTFS handles and supports filenames
with Unicode characters just fine. There are o
On 2020-03-06 9:13 am, Torsten Hämmerle wrote:
Jean ABOU SAMRA wrote
You likely have a special character in the name of your file.
Windows handles this poorly and LilyPond (actually Python,
behind the scenes) can't do much for this. Try removing
special characters from the file name,
Hi again
I could indeed solve the issue by changing the filename to another ;-))
Another issue was that musicxml2ly on windows 10 could not open
compressed xml files (zlib module missing). But that it is not a big
problem. Uncompressed worked OK.
So now I can continue my work with an adapte
Jean ABOU SAMRA wrote
>You likely have a special character in the name of your file.
>Windows handles this poorly and LilyPond (actually Python,
>behind the scenes) can't do much for this. Try removing
>special characters from the file name, it should solve
>your problem.
I ca
> Hi
> I have for some time as a musicshool teacher been a busy user
> of lilypond on my Linux Desktop. Recently my employer have forced
> me to work on windows 10. I have got a working setup but
> musicxml2ly gives the following error:
>
> Starting python-windows.exe...
Hi
I have for some time as a musicshool teacher been a busy user of lilypond on my
Linux Desktop. Recently my employer have forced me to work on windows 10. I
have got a working setup but musicxml2ly gives the following error:
Starting python-windows.exe...
Traceback (most recent call last):
F
