Copy/Save FileDetails: problem with ft_numeric_32 types

The behaviour described in the bug report is either by design, or would be far too complex/time-consuming to be changed

Moderators: white, Hacker, petermad, Stefan2

Post Reply
User avatar
petergus
Member
Member
Posts: 164
Joined: 2003-02-06, 16:28 UTC
Location: Sweden, Enköping
Contact:

Copy/Save FileDetails: problem with ft_numeric_32 types

Post by *petergus »

I use space (#32) as a ThousandDelimiter.

I did some test using a built-in function and Lefteous DirSizeCalc:

[=tc.size] [=dirsizecalc.Size (Background)]

My ThousandDelimiter is shown as a space in TC and on the
exported data. But when I check it closer, it's not #32 it's #160.

The same with cm_SaveDetailsToFile.
Peter, Personal licence #84319
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48232
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

Can anyone reproduce this problem?
Author of Total Commander
https://www.ghisler.com
User avatar
Flint
Power Member
Power Member
Posts: 3487
Joined: 2003-10-27, 09:25 UTC
Location: Antalya, Turkey
Contact:

Post by *Flint »

petergus
Are you sure you are using space as a delimiter? At first I too thought that it is a space (#32), but now I checked the settings (I'm using the default Russian locale) and found that a non-breaking space (#160) is specified there! I changed it into normal space, restarted TC and it began to use the space (#32) as a delimiter. After I restored #160 TC too uses #160.

So, I cannot confirm the bug.
Flint's Homepage: Full TC Russification Package, VirtualDisk, NTFS Links, NoClose Replacer, and other stuff!
 
Using TC 10.52 / Win10 x64
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48232
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

Thanks, Flint!

2petergus
Can you confirm that?
Author of Total Commander
https://www.ghisler.com
Post Reply