Closed zabelhaft closed 9 years ago
yes but i think we dont need it, see allowed characters:
FS | Allowed characters in filenames | |
---|---|---|
NTFS | In POSIX namespace, any UTF-16 code unit (case-sensitive) except U+0000 (NUL) and / (slash). In Win32 namespace, any UTF-16 code unit (case-insensitive) except U+0000 (NUL) / (slash) \ (backslash) : (colon) * (asterisk) ? (Question mark) " (quote) < (less than) > (greater than) and | (pipe) |
HFS Plus | Unicode, any character, including NUL. OS APIs may limit some characters for legacy reasons |
and because those characters are catched by http://beets.readthedocs.org/en/latest/reference/config.html?highlight=trailing#replace
i'd link to change
replace:
'^\.': _
to
replace:
'^\.':
though, to remove any trailing dots and not replace them by _
on the other hand, ascii paths would be probalby better searchable in the file managers
i added the default values in the config.yaml
feel free to change the trailing dot behaviour
done (damn, missed to mention the issue in the commit)
i dont know, right now we even have cyrillic folder/file names...
since we usually use itunes (or other programs) which handle stuff like this (e.g. map e
to é
) i think we should have the most accurate folder/file structure possible... i guess?
trust in unicode! #close
On Friday, June 12, 2015, Kai notifications@github.com wrote:
done (damn, missed to mention the issue in the commit)
ascii:
i dont know, right now we even have cyrillic folder/file names...
since we usually use itunes (or other programs) which handle stuff like this (e.g. map e to é) i think we should have the most accurate folder/file structure possible... i guess?
— Reply to this email directly or view it on GitHub https://github.com/Schweinepriester/beets-config/issues/11#issuecomment-111489208 .
http://beets.readthedocs.org/en/latest/reference/config.html#asciify-paths
another useful feature?