There can be no collisions anyway, since ZPAQ and the format specification always makes sure that each version differs by at least one second, so a single timestamp string is enough to make names not colliding anywhere.Hacker wrote:of course, for the <timestamp> part the existing custom date string can be used, just surround it by < > so that there are no possible collisions
I don't like putting forbidden characters anywhere, that's why I wrote "WYSIWYG" (what you see is what you get). Users may be confused that the name isn't extracted like it was seen in the archive.
And BTW, if I'd use that very string from the "Show archive version names as detailed timestamp" option, users are free to put anything before and after the main timestamp anyway. So you may put similar looking characters from the Unicode plane in this string by yourself w/o worrying about them being deleted or replaced, like I suggested here:
Anyway, I will need to give this some thought.
I understood that, but like I said: I need to treat dir names internally as case-insensitive anway. So, no matter if I try to separate dirs or not, they'd end up in the same location.Hacker wrote:Well, as I wrote, two options:
a) latest name ("dirECTory")
b) name with <timestamp>
The b) option is not doable anyway, because I can't list an individual file on more than one location and making it possibly extract twice (the same reason why the "Show the default archive view in extra dir" option "moves" the newest files to that extra dir).
I need to check if this would be possible, but again: violation of WYSIWYG.Hacker wrote:I would just like to add, if I extract Filename.docx from version 52, please also use dirname from version 52 and dir timestamp from version 52.
And when extracting a file when the output dir exists but differs in case, Windows API functions (which ZPAQ uses) would of course keep the old dir name, just like when overwriting case-differing files/dirs in TC.