-
-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Support for Multiple Number Formats (Comma or Point as Decimal Separator) #37
Comments
Yeap. True. I also was thinking about it before starting the coding. I decided to go with a dot at decimal point. Using both, dot and comma. Make thinks very unclear without specifying a locale. For example: 100,005 what is this number? |
This has been bugging me a lot, especially when I copy paste numbers from other places. They paste as wrong format and then it's manual labor to correct them all. If I may suggest two solutions:
|
Like:
|
Maybe But if an URL param is not an option, |
I'm thinking to add this in doc itself. In params section:
|
Just thinking about adding config lines directly in the document itself. It's cool for control, but might clutter things up for folks sharing docs, especially if their audience isn't tech-savvy or fluent in English. How about to auto-hide those config lines when a document is opened? You could add a "Show Configs" button for anyone wanting to edit them. Keeps things clean for most users while still flexible for those who need it. |
Yeap. I’m thinking about hiding config. |
I'm writing to request enhanced support for various number formats in Numbr, particularly for the use of the comma as either a decimal separator or a thousands separator. Currently, the platform seems to predominantly support the format where a comma serves one specific role (as a thousands separator), which aligns with the practices of several regions. However, a significant portion of the global population uses a format where the comma acts as a decimal separator, leading to potential confusion and data interpretation errors.
I propose the introduction of functionality that allows users to choose their preferred number formatting style. This could involve toggling between:
The text was updated successfully, but these errors were encountered: