Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


One Album will not Play
#11
Many of these naming issues arise because of the habit of constructing filenames from track metadata. There's not enough filtering to make the resulting names acceptable to various operating systems.

While the Linux filesystem is very permissive, the Linux interactive shell (like the RaspberryPi OS's default "bash") and related scripts do, um, interesting things when they encounter certain characters. While it is possible to escape most, it is difficult to ensure that this is done consistently.

The situation is worse in MS Windows and I would suggest users restrict their names to the Windows conventions to avoid issues moving files between different systems and servers.

Here's a quote from the Microsoft site concerning file and directory naming 

Quote:Use any character in the current code page for a name, including Unicode characters and characters in the extended character set (128–255), except for the following:

The following reserved characters:

< (less than)
> (greater than)
: (colon)
" (double quote)
/ (forward slash)
\ (backslash)
| (vertical bar or pipe)
? (question mark)
* (asterisk)
Integer value zero, sometimes referred to as the ASCII NUL character.

...

Do not end a file or directory name with a space or a period. Although the underlying file system may support such names, the Windows shell and user interface does not.

Of these, only the solidus (forward slash) is explicitly excluded in Linux but IMHO they all should be avoided regardless.


Regards,
Kent

PS - never used MacOS so can't speak to it.
Reply


Forum Jump: