Page MenuHomePhabricator

Correct SI unit "KB" into "kB" or IEC unit "KiB"
Closed, DeclinedPublic

Description

I go to the page http://phabricator.wikimedia.org/file
I see many files, with their size, in "KB".

There is no such thing as a "KB".

This has to corrected into one of these:

  1. kB: kilobyte(s): 1 kilobyte = 1000 bytes
  1. KiB: kibibyte(s): 1 kibibyte = 1024 bytes

Thank you.

Nnemo

[Edit:]

I choose a file. I click File Info.

The issue also occurs here.

Nnemo

Event Timeline

Nnemo raised the priority of this task from to Needs Triage.
Nnemo updated the task description. (Show Details)
Nnemo added a project: Phabricator.
Nnemo added a subscriber: Nnemo.
Aklapper edited projects, added Phabricator (Upstream); removed Phabricator.
Aklapper set Security to None.

I choose a file. Then I click File Info.

The issue also occurs here.

The spell check that is used by Firefox recognizes KB as valid, however, it does not recognize KiB.

Related thought: There should be a #pedantic tag for tasks like this one.

epriestley added a subscriber: epriestley.

The upstream is exceedingly unlikely to change this. Although "KB" is not a technically precise unit, it is widely understood by users and is the unit used by both MacOS ("KB" in "Size" column) and Windows ("GB" in "Disk Space" readout) to identify filesizes:

Screen Shot 2019-05-19 at 2.46.36 PM.png (227×922 px, 81 KB)

Mybuj.jpg (626×971 px, 78 KB)

In almost all contexts, normal users do not care (and do not make decisions differently) if "GB" means 1,000,000,000 bytes or 1,073,741,824 bytes and the distinction is ultimately irrelevant.

Generally, we are eager to trade away pedantic technical correctness to serve almost any other goal (ease of use, familiarity, simplicity of implementation, etc), and are very unlikely to make changes which serve only pedantic correctness concerns.

Aklapper renamed this task from Correct KB into kB or KiB to Correct SI unit "KB" into "kB" or IEC unit "KiB".May 22 2019, 12:52 PM
Aklapper closed this task as Declined.

Thanks for the feedback, Evan!

We don't plan to maintain a downstream patch for this either, hence closing as declined.