[tahoe-lafs-trac-stream] [tahoe-lafs] #964: show sizes in unambiguous way that doesn't get mistaken for different units

[tahoe-lafs]

#964: show sizes in unambiguous way that doesn't get mistaken for different units
------------------------------+-----------------------
     Reporter:  USSJoin       |      Owner:  zooko
         Type:  defect        |     Status:  assigned
     Priority:  minor         |  Milestone:  undecided
    Component:  code-storage  |    Version:  1.6.0
   Resolution:                |   Keywords:  usability
Launchpad Bug:                |
------------------------------+-----------------------

Comment (by zooko):

 Replying to [comment:14 Zancas]:
 > > We will continue to use {{{KiB}}} to mean 10^3^, {{{MiB}}} to mean
 10^6^, {{{GiB}}} to mean 10^9^, {{{TiB}}} to mean 10^12^ etc. as per
 http://en.wikipedia.org/wiki/Binary_prefix , and never use {{{KB}}} to
 mean 2^10^ etc.. However, as per the ''main idea'', above, we will
 probably try to reduce the use of {{{KB}}} at all in favor of less
 ambiguous designations.
 >
 >   Oops....   isn't it {{{KiB}}} means 2^10^...  et cetera?   If I
 Understand Correctly the infixed "i" means base 2, and exponent increments
 of 10.

 Argh! How did I screw that up‽ Thanks, Zancas, for noticing. Everyone
 reading this: disregard what I wrote and just believe that we're going to
 do what http://en.wikipedia.org/wiki/Binary_prefix says about how to spell
 the base-2 things. Also, as previously mentioned [comment:11 on this
 ticket], spelling out numbers with commas in place is unambiguous and is
 the standard format for integers in Internet English writing.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/964#comment:15>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage