[PATCH] Add support for JEDEC/metric standards to KLocale::formatByteSize
mboquien at free.fr
Fri Jul 24 20:40:43 BST 2009
On Friday 24 July 2009 15:28:38 Matthew Woehlke wrote:
> Michael Pyne wrote:
> > 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.
> All three are identical in Terminus ;-). The above sounds like a bug
> that should be reported to the author of the font in question.
That is most likely because the glyph is not in the font, so it is taken from
another font which does not have the same metric. It is not reallt a bug in
the font but it is just that the font is not complete enough. Hence the
advantage to use a font that has a wide unicode coverage.
More information about the kde-core-devel