I suggest ...

Normalize filenames, i.e. replace umlauts and special characters

In order to be best compatible with different systems (Windows, Mac, Linux) or different file systems, it would be nice if bliss would be able to use a limited character set for naming directories and files.

Syncing different systems if e.g. file names contain umlauts like "Die Ärzte" sometimes causes problems, because the files are not considered to be the same by the synchronization software.

Different systems also have different file name restrictions, e.g. Windows does not allow colons, while Linux does. On the Mac, colons in file names are somehow treated as forward slashes.

I would really like bliss to handle all the naming of files and directories from the tags, but only if bliss can be told to perform an umlaut replacement (e.g. remove all diacritical marks and remove or replace all special characters).

Thanks
Carsten

23 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Carsten shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    12 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Len commented  ·   ·  Flag as inappropriate

        Oops, mistyped - I meant OS proscribed characters :)

        It wasn't immediately clear to me that you were only taking on board the special characters (of which windows has far too many, but that is another discussion) rather than considering purging accented characters which I think was the original thrust of this request. UFT-8 has to be the way to go and other software packages should step up to it rather than damaging international support by attempting the horrible task of filtering out accented character.

      • AdminDan Gravell (Founder and programmer, bliss) commented  ·   ·  Flag as inappropriate

        They were asking for both - I was answering the special character case. We already support UTF-8. What do you mean by "OS prescribed symbols"? Are you saying there are characters from the non-Latin set that aren't permitted? If so, please send me a URL!

      • Len commented  ·   ·  Flag as inappropriate

        Replacing special characters which cause the filesystem to glitch is one thing and is probably an unfortunate necessity due to the way Windoze works, but the OP was asking for umlauts and diacriticals to also be removed. These are not special characters to many non-English speakers, but an integral part of their language. The correct solution is to support UTF-8 and filter only OS-prescribed symbols. Most browsers and major software packages can already handle UTF-8 so the support infrastructure is already in place.

        For the record, I am English and have no need for accented characters except when being anal about loan-words, but we really need to avoid the sort of linguistic imperialism which tells others that they don't need part of their alphabet.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Hi Dan,

        theoretically, the option that controls Ripit's replacement behaviour for special character is [chars], which will identify characters that Ripit will purge from the filenames but not the Tags. Regardless of the setting, the following character will always be removed:

        ; > < " and \015

        At least on my standard Vortexbox install [chars] is set as follows

        chars=NTFS

        which would result in these additional removed characters

        | \ : * ? $

        What I found to be the case on my system (and I haven't seen anything about it in the Ripit documentation yet) is, that any / will be replaced by -
        So songs that have multiple names in one track like "something / something else" will become "something - something else", while Bliss thinks those should me removed as well: "something something else"

      • Anonymous commented  ·   ·  Flag as inappropriate

        I strongly support this feature request as well. When ripping with ripit on a Vortexbox often the character replacement that bliss expects is different from the one that ripit does resulting in wrong file name detections in bliss.

      • Christoph commented  ·   ·  Flag as inappropriate

        I want to strongly support this feature request. It's not just a matter of compatibility with different operating systems but must importantly a matter of making your songs compatible with MusicIP. If I'm not mistaken, MusicIP (and hence also Spicefly Sugarcube) will not work with songs that have non-ascii characters in their path. Since MusicIP is no longer developed, the only way to fix this is by not using umlauts etc. Bliss could do an excellent job to fix that.

      • Jim commented  ·   ·  Flag as inappropriate

        or maybe make it remove and special characters all together as an option

      • Jim commented  ·   ·  Flag as inappropriate

        I would also like to see this, i have had lots of troubles with just apostrophes getting viewed as a question mark or a dash getting changed to a question mark

      • Kevin Bryan commented  ·   ·  Flag as inappropriate

        I need something along the same lines. Some band names and song titles contain characters that cannot be used in Windows file systems, such as "/" and "?". Currently, bliss deletes any character it doesn't understand from the filename. I would like to see bliss let me tell it through a list to replace invalid characters with a consistent valid one of my choosing.

      Feedback and Knowledge Base