We're reviewed this issue, and are reconsidering the correct solution.
As we understand it, each client has one 'correct' decimal point character which is derived from it's locale (specified in the operating system, and possible overridden by the browser).
We think that a solution whereby the client parses and displays number input based on the locale (starting with decimal point now), should be sufficient.
To that end, can you please check on your different client targets, whether the url javascript:alert(1.5.toLocaleString()) returns the correct result (decimal point).
Your comments on this will be appreciated.
Regards,
David
To use the full functionality of this web site, JavaScript needs to be turned on.
For best results, use the Firefox browser..
Copyright © 2003-2017 - Tersus Software Ltd., All rights reserved. Terms of Use License Graphic design by EmaraDesign
