Parts export filenames with flat signs
Hi,
I have an orchestral score with instruments like Bb Trumpet and Bb Clarinet.
The "Bb" is using an UTF-8 character for the "flat" sign (how do I type such a character in this forum's texteditor?)
When automatically exporting the separate parts from the score, also the filenames have those special UTF-8 characters in the filename. This may be allowed on modern filesystems, but I find them very unpractical. And some filesystems may have trouble with such filenames.
Would it be possible to let Musescore automatically replace the UTF-8 Flat character with a "b" when constructing filenames when saving? Same story for Sharp character and "#".
Comments
It sure would be possible to get MuseScore to replace those. We do this for some characters already, like German umlauts (öäüÄÜÖ). Mind to file an issue for it, at https://musescore.org/en/node/add/project-issue/musescore?
In reply to It sure would be possible to by Jojo-Schmitz
Please don't. File names in POSIX-compliant operating systems are sequences of bytes.
There's little use in keeping MuseScore MS-DOS compatible ....
Even worse: substituting ♯ with # will create a file name containing the POSIX shell comment character. Not smart ...
In reply to Please don't. File names in by rmattes
a # in a filename is not problem at all. Unicode/UTF-8 characters definitly are a Problem, they are not bytes but shorts, POSIX allows anything in 8-bit ASCII excluding the / and the \0.
having a # in a filename is far easier to handle than a backspace or linefeed. Even easier than spaces, at least if it isn't the 1st char (after a space)
In reply to a # in a filename is not by Jojo-Schmitz
POSIX allows anything in 8-bit ASCII excluding the / and the \0.
No, that's where may err - POSIX specifies filenames as sequences of 'char' with the exception of the tow chars you allready mentioned, there is no encoding semantic implied anywhere (btw. ASCII is 7-bit ...). Unless you refer to the Open Group's "Portable Character Set", but that is ridiciously limited.
What actual problem are we solving by replacing ♯ with a number sign and a ♭ with the letter b?
In reply to POSIX allows anything in by rmattes
see OP:
This may be allowed on modern filesystems, but I find them very unpractical. And some filesystems may have trouble with such filenames.
They may be sequences of Bytes, but whether they are displayed correctly be whatever means the OS might have (Windows Exploter, UNIX ls, etc.) is an entirely different story.
Have an umlaut in a filename in Windows, upload to an FTP Server (presumably running Linux) and what the wreckage.
Some more cracters are disallowed on Windows FAT/NTFS and replaced by an _ in MuseScore, "\\/:*?\"<>|". Remember we need to remain platform indepentant, as much as we can.
If you want any of these chars in a filename, you can use them, but MuseScore should not do this by default.
The sharp character is not used in any instrument name, so not likely to cause any problem.
Unless when use in the title of a score...