Very old bug: TC+UC2

[DrShark]

Currently not possible to use UC2 (list of archive, view, unpack) from TC if archive placed in path with special chars alike &.
If path to User profile under XP contain &,
working with UC2 inpossible anyway.
Reason: TC calls UC2 like here:
UC V c:\progra~1\file.uc2
To fix problem, TC should use quotes:
UC V "c:\progra~1\file.uc2"
This is very little change. But Christian don't want to fix this because UC2 format is unpopular and it's developing stopped lot of years ago. For me, "unpopular" - advantage. It would be nice to support encrypting via TC if UCRYPT.EXE placed in UC.exe dir too...

[ghisler(Author)]

Sounds like a bug in UC2. I will consider this change for a later release.

[ghisler(Author)]

I'm using double quotes now in case of & character. Please test!

[DrShark]

2ghisler(Author)
Fix confirmed in RC4!
Thanks!

[ghisler(Author)]

Thanks for reporting it! Btw, are any other characters causing the problem too? I only add quotes in case of & now...

[DrShark]

I created table for this:
Sign: 8.3: "8.3":
& - +
! + +
; - -
' + +
# + +
[ - -
] - -
{ + +
} + +
' - -
~ + +
` + +
^ - +
$ + +
@ + +
- + +
+ - -
= - -
_ + +
№(ANSI) +* +*
* this is interesting - I saved bat file for this test in ANSI, so cmd.exe converted (or recognized as, while bat file was running) "№" to (as) special dos char (as often using in NFO files). Both XP REN command and UC2 understand it, but I cannot even open such dir in TC.

[ghisler(Author)]

So the only character which would profit would be the ^ character, right?

[DrShark]

So the only character which would profit would be the ^ character, right?

Yes.

And bug still not fixed for case when %temp% contains &

[ghisler(Author)]

OK, ^ character handling added.

And bug still not fixed for case when %temp% contains &.

Sorry, I will not change that. That's something which you can avoid, and you should really avoid it at all cost - other programs may have the same problems with special characters.