-
Notifications
You must be signed in to change notification settings - Fork 0
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
Option for numeric formatting #4
Comments
Thanks for the suggestion. We will add an option for number formatting in the same pane as date/time formatting. |
You may want to check the other things that Apple thinks that are 'smart', like quoting and that. It probably boils down to "raw data" vs "system preferences" ... is that just want tick-box in your configuration ? Thanks for looking into it |
I should elaborate a bit on the precise intended behavior: when Splice sees a number, date, or time in a table, it will format it according to the current localized conventions. I assume that your current locate is one where the thousands separator is a "." (if not, let us know, because then that would be a huge bug!). Note that when copying table rows, or when exporting data, these formatting rules will not be applied: only the "raw" number will be displayed (although the fraction separator will still be locale-dependent). It is only for displaying the numbers to the end user that the locale's formatting rules are applied. All that being said, we will add an option to override the default formatting for numbers in an upcoming version. |
@mprudhom , I can confirm that the formatting of the thousands-separator is correct (no huge bug!). |
Depending on what user-type one is, a 'semi' admin or a 'end-user', one will have different perception of how data is being displayed. I was very surprised to see a number show up as something like '6.030', knowing that it has been '6030' always. And that is what it is in the database.
Please make it such that data is displayed as being stored (no not the binary data itself as a stream of bits), so a database admin is not getting confused. A perfect place would be preferences, where already there is the option to change formatting.
Alternatively, but not acceptable, is changing the system preferences.
The text was updated successfully, but these errors were encountered: