According to the online help the "File Settings" option "Autodetect
charset" determines whether unired tries to detect the charset
automatically. If it is not set, it should use the configured "Default
charset".
This does not work, it tries to autodetect the charset (and fails)
anyway.
Testcase:
The attached file (content: "Thomas Müller") was created
with unired and saved using UTF-8. If I uncheck "Autodetect
charset" and set "Default charset" to UTF-8 I expect unired to load
this file using UTF-8. Instead it detects it (wrongly) as cp-1250.
Logged In: NO
Hm, sorry, the file apparently didn't make it, this is a hex dump of its
content:
54 68 6f 6d 61 73 20 4d c3 bc 6c 6c 65 72 0d 0a
Logged In: NO
OK, this isn't a bug in the program but rather some odd setting in the
default files.ini file:
The "plain text" section also contains "default" which in my opinion is
wrong because that's what the "*" section is for. So what happened was
that I set "Autodetect" to false for "*" but left it to true for "plain text,...,
default" which resulted in unired reading the settings from "*" first but
then overwriting it with the settings from "default" resulting in Autodetect
to be true again.