Problem with reading non-english letters
After updating to version 4.4.0, I couldn't open any .mscz files had non-English letters or .mscz files that were in folders/subfolders that had non-English letters like ä, ñ, č, š, ע etc. The warning I got said ''Cannot read file, this file does not exist or cannot be accesed at the moment''. I renamed the files and folders/subfolders to remove all the non-English letters and now they can all be opened up without a problem. I'm putting this out here so that in case you get the same problem with a file that has non-English letters in its filename or is in a folder that has them, try renaming the file/folder. It could help fix the issue.
Comments
This is a significant issue for me, because I transcribe a lot of classical music and many classical music pieces(like for example Schubert's lieder) have German titles. I was always irked about how MS3 automatically saved ä in the score title as ae in file names and when I noticed that MS4 saved ä as ä, I was very happy. Now that MuseScore 4.4 can't read file names with those German umlauts, I'm understandably, upset about this and I hope it gets fixed!
I can't reproduce. Can you attach one such musescore file?
In reply to I can't reproduce. Can you… by mercuree
Opens up fine in MuseScore 4.3.2, but in MuseScore 4.4, it doesn't open at all and I get this:
All because of that one ä in the file name.
In reply to Opens up fine in MuseScore 4… by Caters
Very interesting... I have windows 10 and it works fine for me.
Maybe someone can figure out what's going on here
In reply to Very interesting... I have… by mercuree
I sure hope so, cause it's frustrating to me that I have to rename the file simply to have the score load. I also have Windows 10.
In reply to Very interesting... I have… by mercuree
I have windows 10 pro and it doesn’t work. I also cannot enter any foreign characters in project properties.
In reply to I have windows 10 pro and it… by tmarcnguyen
Then you have not updated your Musescore.
This problem was present for a limited time, but is over.
Okay, this issue is known to the MuseScore team and the upcoming patch release next week will fix it. Github link:
https://github.com/musescore/MuseScore/issues/23811