In ONLYOFFICE Spreadsheet Editor, even when the regional settings are correctly configured (e.g., Spain or Germany), and the thousand separator is explicitly set to a dot (.) in the Advanced Settings, the default “Number” format does not automatically apply the thousand separator.
The only way to enable it is to manually go to More Formats → Number → check “Use thousand separator”, which is inefficient when working with large datasets or templates that rely on consistent formatting.
I suggest the following improvements:
- The default “Number” format should automatically respect the regional settings, including the thousand and decimal separators.
- If the user sets a custom separator in Advanced Settings, it should be reflected immediately in the default number formatting.
- Optionally, allow users to define and save a preferred number format (with thousand separator) as the default for new spreadsheets.
This would greatly improve usability and align ONLYOFFICE with the behavior of other major spreadsheet editors.
Hello @Davizator51
We are checking the situation, we will contact you shortly.
Hello @Davizator51
The Thousand separator is automatically applied for Currency and Accounting formats. For the Number format the separator is disabled by default, and this is expected behavior.
If you need more flexible format, you can use the Custom, where you can configure the formatting as needed.
If it’s possible, please describe your desired scenario and your idea for changing the established behavior, so we can better understand your scenario.
Hello Alexandre:
Thank you for your response. While I understand that the default behavior for number formats aligns with expectations in certain locales, I’d like to highlight that this logic is based largely on Anglo-American conventions.
In many regions, such as Spain and much of Latin America, the thousand separator is a period (.) and the decimal is a comma (,), which differs from the U.S. format. This default behavior might cause confusion for users working outside of the English-speaking world.
I’d suggest considering more dynamic formatting based on the user’s regional settings or offering a clearer indication that number formats may need customization depending on locale.
Would it be possible to explore a more flexible approach that takes into account the user’s language and system preferences automatically? That way, we could ensure consistency and avoid having users manually reformat their data just to meet regional norms.
Thanks!
Hello @Davizator51
I’m a little bit confused. The regional settings already impact separators:
Please clarify, if i misunderstood your idea.