[Bug 53716] Re: Too generic error message when file names (/encodings?) are not Windows-compatible

[Tuomo Sipola]

I use the newest version 6.06 LTS (fresh install although old home
directory).

I think once using the iso-image tool on terminal it reported files
being non-compliant when the encodings of the file names themselves
where somehow not nice (ie. including some bad characters). The initial
conversion from ISO-xxxx encoding to the UTF-8 of my system when
receiving those files from a Windows machine might have made the names
non-compatible.

I think the problem is the same. As the bug states, I'd like to see
which files are not compatible so that I could easily search them and
rename appropriately.

-- 
Too generic error message when file names (/encodings?) are not Windows-compatible
https://launchpad.net/bugs/53716