Am Donnerstag 01 November 2007 schrieb Thomas Perl:

> I think, gPodder's behaviour should be the following:
>
> - default to SI prefixes (decimal, 1000 bytes = 1 kB)
> - optional: binary prefixes; "1024 et al." (and display "KiB, MiB, ...")
>
> Are there any objections?

Hm, I wouldn’t recommend it. The problem is that the users expect kB as 1024, 
not as 1000.

If they see kB, they expect 1024. I guess it wouldn’t be a problem if they see 
KiB instead of kB. I think they will know that kB is meant, they just wonder 
what the i does there :D

The problem with SI prefixes is the file becomes “bigger”. I guess some people 
would be confused by that.

I would vote for binary prefixes as default and SI as optional. Binary 
prefixes aren’t wrong. It’s just that if SI units are used correctly, but the 
user doesn’t know it, he could wonder why the filesize is different than in 
the file browser.

> That would change the values displayed (without changing the unit's
> name), but as gPodder currently displays "wrong" values, I guess this is
> okay. If people want the current calculation (binary), they can switch
> to it in the config file and have KiB, MiB, etc.. displayed).
>
> That would be the Right Thing(tm) when looking at standards. The changed
> behaviour of gPodder is justified by the fact that currently gPodder
> displays non-standard units/values.

Just again, binary prefixes are not wrong. What’s wrong is just if kilo is 
used as 2^10 or mega as 2^20. A kibibyte with 1024 Byte is completely 
correct. I just believe that some people would rather like the correct SI 
units (But I don’t think that some —sorry– unknown apps like gpodder could 
change the way the users use kilo if Microsoft and Apple do not adapt them) 
if they know the difference.

So in summary (in my opinion) the way would be:
default: leave the way it is now, but change KB, MB and so on to KiB, MiB, GiB
optional: offer SI units with kB as 10^3, MB as 10^6 and so on.

Gerrit
_______________________________________________
gpodder-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/gpodder-devel

Reply via email to