Perhaps transforming it into a localization problem would do the trick. This way, users would be able to set their preference on byte-count in the same place as their preference on currency, decimal, and am/pm vs 24h. Applications could make use of the localization settings to calculate the amount of bytes, which would hopefully eventually centralize and generalize what counting-method the user sees.
David Verhasselt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
