wrong number delimiter

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

Moderators: Hacker, petermad, Stefan2, white

Post Reply
SailorMax
Member
Member
Posts: 121
Joined: 2007-03-15, 15:11 UTC

wrong number delimiter

Post by *SailorMax »

steps:
1. Ctrl-Q on any large directory

expected result sample: 8 520 712 bytes in 1 211 file(s),

my result: 8a520a712 bytes in 1a211 file(s),


Windows XP ENG x86-32, region russian
Total Commander 8.0b16 x86-32
User avatar
Flint
Power Member
Power Member
Posts: 3506
Joined: 2003-10-27, 09:25 UTC
Location: Belgrade, Serbia
Contact:

Post by *Flint »

SailorMax
Most probably you have locale configuration broken in your system. Check for Control Panel -> Regional and Language Options, in the first tab select some different locale, press Apply, then select back Russian, press Apply again. Check the "Number" field for the number representation. If it's still broken, press the "Customize" button and under "Digit grouping symbol" select the space character from the drop-down list (or enter it manually, but you should enter a non-breaking space, that is Alt+0160 using the numpad).
Flint's Homepage: Full TC Russification Package, VirtualDisk, NTFS Links, NoClose Replacer, and other stuff!
 
Using TC 11.03 / Win10 x64
SailorMax
Member
Member
Posts: 121
Joined: 2007-03-15, 15:11 UTC

Post by *SailorMax »

I tried change regional settings but without any positive result.
In any other applications Alt+0160 output as `space`... On other computer with same Windows settings all fine. In Character Map I see it as space also.

Which font do you use in Ctrl-Q window?
SailorMax
Member
Member
Posts: 121
Joined: 2007-03-15, 15:11 UTC

Post by *SailorMax »

Manually change "Digit Grouping" helped! :) thanks!
User avatar
Flint
Power Member
Power Member
Posts: 3506
Joined: 2003-10-27, 09:25 UTC
Location: Belgrade, Serbia
Contact:

Post by *Flint »

SailorMax wrote:In any other applications Alt+0160 output as `space`
It looks like space but it is not really space, it's a non-breaking space. That is, when you insert it, applications will not be able to apply word-wrapping at this position. So, if you write e.g. "8 520 712 bytes" with usual spaces, and this text appears near the right border of the window it may become wrapped like this:
8 520
712 bytes
But if you use non-breaking spaces there instead of usual spaces ("8 520 712 bytes"), this whole string will look the same, but will be treated as a single word. If there's not enough space for it, it will be put to the next line as a whole, without splitting in half.
Flint's Homepage: Full TC Russification Package, VirtualDisk, NTFS Links, NoClose Replacer, and other stuff!
 
Using TC 11.03 / Win10 x64
Post Reply