=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>
> Making a web page about something doesn't make it true.  This hijacking of
> kilobyte is just an attempt to rewrite history, and is as doomed to fail
> as the crusade against calling 2000 the new millennium, or against the
> popular meaning of "hacker."
>
> >  MB is officially 1000000. MiB is 1048576. And people are starting to
> > use MiB instead of the now a bit ambiguous MB when they mean 1048576,
> > albeit slowly.
>
> Some self-appointed group may say at the top of their lungs that a Kibiby=
te
> is officially 1024 bytes, but that doesn't change how stupid that sounds,
> and it doesn't dislodge decades of history.
>
> But the important thing here is the configurability.  Even if you dismiss
> that there is an established tradition for a kilobyte being 1024 bytes,
> you're not going to be able to dismiss other established unit systems so
> easily.
I would say use MB with 1000*1000, MiB with 1024*1024, as the standards say=
s,=20
as these standards are world wide accepted. They are perhaps confusing, but=
=20
who cares ? It is not our thing to make the standards but to use them. (I=20
don't like them, but it is simply correct to use them, but we could come up=
=20
with just an other standard, like 1023*1023 =3D MkdeB ;)).

=2D --=20
Christoph "Crossfire" Cullmann
Kate/KDE developer
cullmann@kde.org
http://kate.kde.org
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9ivEdyPjDGePm9UIRAjQ8AJoDmQWxM3HUFJGwWZfma9BC0bABxQCfX4UD
0VGVnYiP3gr8dmFiZE4wpUY=3D
=3DJGv9
=2D----END PGP SIGNATURE-----