Task #67572

Update calls to formatSize to adjust to new units

Added by Pierrick Caillon almost 6 years ago. Updated over 1 year ago.

Should have
Backend User Interface
Target version:
Start date:
Due date:
% Done:


Estimated time:
TYPO3 Version:
PHP Version:
Sprint Focus:


Follow up of #22175.

The references and documentation in the following file should be updated to reflect the new feature: typo3/sysext/t3editor/res/tsref/tsref.xml

The label for "byteSizeUnits" should be updated in typo3/sysext/lang/locallang_common.xlf to use the IEC prefixes. (Ki Mi …)

The constant value and comment of constant styles.content.uploads should be updated typo3/sysext/css_styled_content/static/constants.txt to reflect the new feature and use "iec" as default.

Related issues

Related to TYPO3 Core - Bug #69380: Set "si" as the default for cObj fileSizesRejectedStefan Froemken2015-08-28

Follows TYPO3 Core - Feature #22175: Filelist should use IEC prefixes and appropriate units for filesize.ClosedPierrick Caillon2010-02-24


Updated by Stefan Froemken almost 6 years ago

Why you want "iec" as default? I have asked my collegues and my friends and no one knows Kibibytes. So IMO that should be an option, but not a default.


Updated by Pierrick Caillon over 5 years ago

Okay, I expect IEC by default because it is an industry standard and helps differentiate between base ten and base two units. Also as follow up to previous request (#22175) for consistency.

However after some reflection and reading it really happens the awareness of this standard had failed to reach people.

Still, in fact, like #69380, size formatting throughout the backend should use some default and the labels should not be defined each times, for consistency. And configurable ones.
Whereas we finally choose the "legacy" ones (base 2 with K M …), iec ones or si ones.
Maybe a "legacy" keyword specifying the same prefix as si but with base two?


Updated by Susanne Moog over 1 year ago

  • Status changed from New to Closed

As previously noted, we won't cahnge to "new" ;) units that still have not become the default.

As for using the same units everywhere:
Basically, the core uses the "byteSizeUnits" everywhere possible - with the exception of the bytes view helper which needed a slightly different list - however, even that is using the same type of units.

So I consider the basic request in this ticket superfluous and the bug as solved and will close the issue.

Also available in: Atom PDF