I've opted to replace 'illegal' characters in track/album titles (as in the filename constructed with said items) with corresponding unicode versions instead of having them replaced with spaces or dashes.
This leads to Headphones either displaying � instead of a ’ (typographical quote) or totally not recognizing the track.
e.g. if the filename contains a ⁄ (NOTE! This is the unicode version of a forward slash which IS allowed in filenames.)
Now I can understand the need to replace illegal characters that actually are not allowed, but I would like to suggest to do allow the recognition of unicode substitutes and optionally even use these to replace said illegal characters. e.g. besides the already mentioned unicode version of the forward slash, using the unicode version ∶ for the illegal : character (yes they are different, the first one is allowed in filenames)
If it were possible to specify these substitutes in a preference page, it also would solve the issue in searching for better versions since these same substition 'rules' could also be used in reverse direction to put the actual 'illegal' characters back into the search terms
I've opted to replace 'illegal' characters in track/album titles (as in the filename constructed with said items) with corresponding unicode versions instead of having them replaced with spaces or dashes.
This leads to Headphones either displaying
�instead of a’(typographical quote) or totally not recognizing the track. e.g. if the filename contains a⁄(NOTE! This is the unicode version of a forward slash which IS allowed in filenames.)Now I can understand the need to replace illegal characters that actually are not allowed, but I would like to suggest to do allow the recognition of unicode substitutes and optionally even use these to replace said illegal characters. e.g. besides the already mentioned unicode version of the forward slash, using the unicode version
∶for the illegal:character (yes they are different, the first one is allowed in filenames)If it were possible to specify these substitutes in a preference page, it also would solve the issue in searching for better versions since these same substition 'rules' could also be used in reverse direction to put the actual 'illegal' characters back into the search terms