I’ve found something today that I consider a bug, but I can imagine that some others would call it a feature request.
I cannot open a certain directory on my SD card. The name of the directory is bad (according to an almost unreadable popup). But if the machine can see that the dir-name is not correct, why does this result in a unreadable directory and not in a readable directory with a corrected name?
This part of the name is where the 2400 pukes:
ASCII:
wijk - C
HEX:
77696A6B20E2808E2D2043
I think it’s the character before the dash that cannot be read, but I’m not sure.
Well then why do some non-default set characters (like ç) still get printed in directories with weird names that are being generated (reported in another issue)?
Because this is destructive and I, personally, wouldn’t want the machine to correct something like that for me ever. There’s many reasons how a character like this may occur in a directory name. If there’s really a problem it’s better not to correct anything and give up graciously. Hence, yes, I am that person who would consider it a feature, I guess.
Oh, of course! Can you maybe take a photo demonstrating the readability of the pop-up window and include it in your original post? That way all the info regarding the issue will be in one place
