Invalid characters show wrong error

[Thany]

When I try to rename a file with invalid characters (a double quote in my case) it says I have to remove the write protection, while there isn't any.

Total Commander should tell me what I'm doing wrong and it should certainly not cancel editing (I was typing quite a long name, which I had to do again)

[Vansumsen]

Hi,
The errors messages are not specifics enough, and their number is too low; a better parsing might be done, but the Author tolds once that should be too complicated...
Don't forget the little button right the edit bar... instead of re-typing the whole command...
Regards
Paul

[Thany]

It's a simple check... just see if the invalid characters are in the filename.

[Clo]

2Thany
Hello !
- Right in that case… But the Author meant (I guess) that parsing all errors types, then display a quite appropriate error message for each should add much fat in the program…
Plus the slowing down...
- There is an old thread about this
- Please, see too this one

Kind regards,
Claude
Clo

[Lefteous]

Explorer shows a hint (sorry, it's in german but the second line should be understandable for everyone) when an invalid character has been entered. The invalid character is catched before appearing on the screen. This way the filename is always valid. In this case explorer behaves in a good way - this should be applied in Total Commander.

[SanskritFritz]

Well the problem is not with entering new wrong characters, but with editing an existing filename. This can happen for example if one switches codepage in windows, then some accented characters do not appear correctly, and windows tries to convert, but fails. In this case the solution is (if code page switch is not possible) to rename the file on the Command Prompt, like this:
ren some?char.txt normal.txt
where the question mark stands for the problemous character.

[Thany]

SanskritFritz, that is not my case. However, you may be right. At least in win9x, in NT high-ascii characters would automagically become unicode, if not already.

My problem really is with entering new characters. I simply edit a filname and enter a double-quotation mark. Of course, such a character must not appear in a filename and the rename action will fail on winapi level. The problem is that totcmd does not either prevent me from entering such characters, or warn me about it.

On top of that, totcmd should not cancel editing, as this reverts the filename back to the original, which can be quite annoying with very long filenames.

[SanskritFritz]

When I try to rename a file with invalid characters...

Oh, I understood you like "When I try to rename a file with invalid characters in it...
Anyway, you are right, but this never occured to me, why would you like to enter invalid characters into a filename?

At least in win9x, in NT high-ascii characters would automagically become unicode, if not already.

No, I experienced this often on new XP installations, when the regional setting was still english, and I tried to read from the backup CD written under hungarian settings.

[Thany]

Anyway, you are right, but this never occured to me, why would you like to enter invalid characters into a filename?

I don't, but I just didn't realize the character in question was invalid. And who knows what more characters are invalid (I know, but an avarage user may not know).

[Lefteous]

2SanskritFritz

why would you like to enter invalid characters into a filename?

A good example could be pasting a filename from a document title which contains one of the forbidden characters. This happens to me from time to time.

[SanskritFritz]

2Lefteous
Hmm, yes that actually happened to me also.