FTP Filesizes should be displayed with Thousands Separators (10000 -> 10,000) Currently, filesizes larger than 100 kb are very hard to determine by a factor of at least ten. There might be a bug out there for something similar for message sizes. This is important for usability. Quick: What size is 63538937 bytes? PS. Not a dupe of bug 99169 since that one is about "...to nicefy them [ie, large files] to the closest kilobyte...".

If this is done, please make sure that you display the numbers properly per locale. Showing 90,000 in a European locale when 90000 is meant is bad.

We don't have i18n numeric formatting code, I think, which is why I didn't do this in the first place.

Well, then mozilla.org needs to implement "i18n numeric formatting code"; and then mark this bug as being dependant on whatever bug number that implementation has. <rant> Numbers without thousands separators has been annoying the heck out of me since MS DOS 3. I can't believe some software still hasn't abolished this aberration of hard-to-read numbers. <rant/>

Its a legacy problem, believe it or not. Nobody had problems reading the displays until UNIX started displaying MB sized files in bytes...

Moving to future. Assuming a sensible API, this will be easy one bug 108689 is fixed, and its possible to do this.

Personally I would prefer to see file sizes in with a suitable ISO suffix e.g. up to 2047 in bytes, 2048 to 2097151 in KB, 2097152 and above in MB

Neil: I tried that, and it end up making the listings hard to read. The problem with mixing units is that it's no longer possible to glance down the 'file size' column and guestimate the file sizes, because you can't rely on the number of digits in the number as an indicate of file size. It turns out that having everything in K is much clearer.

bug 58610 is probably a duplicate of this bug.

Yep. *** This bug has been marked as a duplicate of 58610 ***

VERIFIED