Storing filenames in QString: a bad idea?

[wysota]

I dont think I quite understand your suggestion about detecting encoding from filepath.

Do you mean I should read the directory with native os-calls to get the raw filename, guess the encoding based on that byte sequence and figure out som way of making that into a QString?

I mean to use statistics to guess what the encoding of the filename is and then to normalize names by converting them to Unicode.

If that suceeds i still can't use QFile to open, because it will use utf-8 when converting the QString filename to char *. So I would ... need to keep the filename as a QByteArray too so I can open the file with native os-calls and promote the FILE * to a QFile later. This is getting messy

Be aware that "down the well" QFile uses platform dependent means to access files and that was what I meant in my previous post.