Please add Optional Separator in numbers frontend representation #7808
Replies: 3 comments 5 replies
-
Do you think this should be per-user, per-device, or per-configuration? |
Beta Was this translation helpful? Give feedback.
-
yes, I was thinking about that too Zack, per user in the profile settings. I do think this (the frontend) should be in the hands of the end-user ultimately. Since per 118 the frontend manipulates the outcome of our carefully composed templates, more options for the enduser would be very much appreciated. I know there are options planned I the backend templates for this too, but have no knowledge of how this would then be represented in the frontend. Anyways, a final option in the profile would fix this 100%. and just to show you why this is not a personal thing, but the common style used in my language setting: or in English btw: not a single separator in sight.. |
Beta Was this translation helpful? Give feedback.
-
+1 here in Belgium same thing |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Since we now have formatted numbers, and an issue report on that #7745, leading to a lot of response which was abruptly closed, please consider adding an option for the separator.
I'd really love to get the actual value in the frontend, instead of a formatted presentation of that. Fully aware many users might not care, or indeed want the separator. I feel there is a strong use case not to use the separator, and would hope something like the excel option for a separator (scheidingsteken) could be possible:
when a backend value is 6551
I would like the template
to show that in the frontend
and not
my pardon for the non matching numbers, Sun just hit the Laundry...
Beta Was this translation helpful? Give feedback.
All reactions