[PATCH] Add support for JEDEC/metric standards to KLocale::formatByteSize
mpyne at kde.org
Fri Jul 24 02:11:47 BST 2009
On Thursday 23 July 2009 18:52:32 John Tapsell wrote:
> For the spacing between the number and the unit, we currently use a
> fullspace, whereas a thin space is considered typographically better.
> The four main possibilities are:
> 34 KiB <-- ordinary space
> 34 KiB <-- THIN SPACE
> 34 KiB <-- HAIR SPACE
> 34KiB <-- nothing
Sounds alright to me (although I'll note there was absolutely no noticable
difference between thin and ordinary space until I looked in a monospaced
font, where thin spaces completely break the "monospacing". I'm not sure if
that's a huge concern though.
> If we do go for a thinspace, it would be nice to have a "formatRate()"
> function as well, that returned: "%1 s⁻¹" so that this can
> consistently follow how we set the spacing and how we format the time
> as 1/s or s⁻¹.
We need a formatRate function anyways. It's on my TODO list since it's
apparently not on anyone else's. ;)
- Michael Pyne
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 836 bytes
Desc: This is a digitally signed message part.
More information about the kde-core-devel