You are viewing a single comment's thread:
There are often going to be odd "bugs" in a system, particularly when it is created by people all over the planet. I used to work with "globalization" in the IT field 20-25 years ago, and even though everyone is technically speaking beholden to ISO numerical/textual conventions, invariably someone's native conventions sneak into the mix.
For example, ten million (correct to 8 decimals, so we have 8 digits on both sides of the decimal) is written:
10.000.000,000000000 in Sweden.
10,000,000.000000000 in USA.
10,000,000.000,000,00 in some parts of Asia and South America
1,00,00,000.000000000 in India and other parts of central Asia
All it takes is one coder somewhere to mistakenly lapse into their "native" system rather than ISO Standard, and you have an undesirable result. Most likely, you will not get an actual ERROR because the digits are valid, just not where you want them.
And very likely, it's not YOU, since you are basically leveraging someone else's code. Could be at Ecency, or Hive-Engine, or in the original PIMP setup.
P.S.: I'm NOT a coder! I just use "pattern recognition" a lot.
Edited to add: To make things tricker, also remember that some communities have a "tax" on payouts to posts created somewhere that is NOT their own front end. Not saying that applies here, but it often accounts for 10-50% differences posted on different sites.
Posted using Tribaldex Blog
I always took the lack of separators in USA formatted numbers as first an optimization by the original implementer in early days of computing that were formatting for money and then there after they took the implementation as the specification afterward. Older hand written texts did use commas in numbers after the decimal point. In South America they use commas for the decimal point and decimal points as separators. If that doesn't confuse you their language will. :D