How to get rid of bad chrs?
Ralf Mardorf
kde.lists at yahoo.com
Mon Aug 2 16:58:13 UTC 2021
I'm strictly against parsing terabytes of directory entries to
automatically rename them, before a backup was made.
Even if nothing should go wrong, no data should get lost, useful names
might become completely useless.
cooking+garlic.txt #for cooking with garlic
cooking-garlic.txt #for cooking without garlic
could become
cooking_garlic1.txt #which text is now for...
cooking_garlic2.txt #...cooking with garlic?
So at least write a log
Was Renamed to
cooking+garlic.txt cooking_garlic1.txt
If software was used to sort files, e.g. photo software that keeps the
file system items as they are, but it provides features with virtual
folders, tags, favorites, the data base becomes useless.
IMHO renaming the items is not the solution, it's asking for way more
trouble. The problems rikona does experience are easy to solve. A real
permission or item name issue doesn't exist. It much likely is caused
by coping data from a UNIX file system that stores permissions,
attributes and allows more chars to a crappy Microsoft file system.
More information about the ubuntu-users
mailing list