Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parts are not loaded for uncompressed format if the file path contains unicode characters #26683

Open
4 tasks done
mercuree opened this issue Feb 22, 2025 · 0 comments
Open
4 tasks done
Labels
regression MS3 Regression from MS3 (3.6.2)

Comments

@mercuree
Copy link
Contributor

mercuree commented Feb 22, 2025

Issue type

Opening/saving issue

Description with steps to reproduce

  • This issue only applies to uncompressed mscx format.
  • Parts are completely ignored. If new parts are generated, they will overwrite the old ones that failed to load.
  • This issue is based on a report from https://musescore.org/en/node/375290
  • I could reproduce the issue since at least version 4.0.2
  1. Create folder with unicode character in its name, for example file name with en dash mark: Weiss, Sylvius Leopold 1687–1750
  2. Create empty score
  3. Open parts and click "Open all"
  4. Go to File -> Save as
  5. Select previously created folder with unicode character
  6. Select file type: Uncompressed Musescore folder (experimental) (*.), remove .mscz from the file name.
  7. Click save.
  8. Close file
  9. Open .mscx file
  10. No parts were loaded

Supporting files, videos and screenshots

Path with no unicode characters (parts are loaded):

Image

Path contains unicode characters (no parts)

Image

What is the latest version of MuseScore Studio where this issue is present?

MuseScore Studio version (64-bit): 4.5.0-250510404, revision: github-musescore-musescore-8b8d44b

Regression

Yes, this used to work in MuseScore 3.x and now is broken

Operating system

windows 10

Additional context

No response

Checklist

  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible
@muse-bot muse-bot added the regression MS3 Regression from MS3 (3.6.2) label Feb 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
regression MS3 Regression from MS3 (3.6.2)
Projects
None yet
Development

No branches or pull requests

2 participants