Valid Windows file names are not all valid linux file names. For example Windows tolerates the apostrophe, linux does not. To help bring awareness of potential issues with software, mark invalid file names in red. Better yet, add an option in the renamer to remove invalid characters from invalid file names. In fact, I would add a dedicated menu "fix invalid file names" in thunar itself. So how do problems manifest. For example, if one tries to extract a file with an invalid file name nothing happens....regardless of which software is used. The layman would have no idea why. But this fix, the layman would say that certain file names are in red, may explore the thunar menu and find the menu named fix invalid file names. Make sense?
(In reply to e.laferriere1 from comment #0) > Valid Windows file names are not all valid linux file names. > For example Windows tolerates the apostrophe, linux does not. I just created a file named: "'##'''¸¸```.txt" ... apostrophe seems not to be a problem. Probably a matter of the filesastem .. using ext4 here. Maybe you have something like FAT ? > So how do problems manifest. > For example, if one tries to extract a file with an invalid file name > nothing happens....regardless of which software is used. ... Nothing happens? So after extraction, there is no file ? .... how should thunar mark something red, if there is nothing to be marked ? Probably best would be to provide a screenshot of what you currently see in thunar/in the terminal after extraction in order to see whats going on.
Closing the bug, since there is no further notice from the reporter on how exactly the proposed feature could look like