Bug in import nzb

[Killer Skunk]

if the filename ends withthe nzb is explained to be empty, my guess is it's triggers some wildcard logic and fails to solve it.

[alex]

it is an unicode nzb filename then, i'll check what is possible.

[alex]

is it possible to avoid nzb names with unicode characters? usenet itself doesn't support unicode.

since if not to compile with unicode enabled it replaces unicode characters with ? (ascii 63 question sign), so when you click the file it basically gets the wrong name, cannot open the file which causes this error message.

i haven't figured out yet how to get the right name without compiling everything with unicode, if to compile everything lot of things may be broken, since it handles lot of lists, like file paths per newsgroup etc., default folders for unpack, and i cannot also just compile since there are errors when converting strings, the strings are no more just sequence of 1 byte characters. the babel tower problem

but at least i will add a warning when the file name contains question signs, since then the windows file name becomes illegal, so the error message will be more specific.

[alex]

In the upcoming v7.8.3d it will display proper warnings, as of now it presumes it always opened the nzb file, but in this case of course it doesn't happen, since the file name supplied by the system is different from the actual file name so it is useless.