[9.21a] "Cannot open file for reading!" message with truncated file path

[MVV]

I've packed some large folder and got a error message "Cannot open file for reading!" with some file path that was truncated because of small window and single-line label w/o tooltip, so there is no way to see full path, I can only guess it. There should be at least a tooltip, but it be also nice to be able to resize such windows...

[Usher]

Was that TC or plugin error message? How did you manage to pack your files?

[MVV]

It is internal TC message that is in LNG file, I've packed into TAR using internal TC compressor. I believe that error was caused by long paths, but it doesn't matter, the fact is that long paths in error message are unreadable.

[Usher]

There might be also problems with Russian/accented characters or total size greater than 2 GiB…

[MVV]

As I said, it doesn't matter what kind of problem occurred, the reported problem is that the path in message cannot be read.

BTW, then I've packed same folder into TAR using 7-Zip w/o any problems. I believe that TC couldn't pack it because of paths longer than MAX_PATH, but I know that TARs support long paths. Also I've just noticed that 7-Zip stores UTF-8 names in TARs while TC stores ANSI names, and TC is able to read TAR created with 7-Zip so it should also be able to pack UTF-8 names to get rid of possible Unicode problems. But I don't use TARs usually and don't pack with TC usually, so it doesn't bother me.

[Usher]

It looks like tar/untar code in TC is outdated. However, there are still possible incompatibilities in different implementations. The problems which I have mentioned (or similar), were reported in 7-zip forum in last few years so watch your step…

[MVV]

I believe that the same error message is used for other archive types too, so it is not related to TAR exclusively.

[Usher]

Well, there's no place for "believe" in the world of facts
Trust no one, even yourself.