Not following system number formatting

[mgw2013]

Steps to reproduce

Numbers not displayed in correct format or app not observing system settings.

Example: system setting German language => decimal point should be a comma.

Missing formatting for large numbers.

Example: 1000000 should be displayed 1{required blank}000{required blank}000 as used in international formats or observe system language setting, e.g. German => 1.000.000

Expected behavior

See steps to reproduce

Actual behavior

See steps to reproduce

Calc You version

3.0 FDroid

Android version

15

Other details

No response

Acknowledgements

• I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
• I have written a short but informative title.
• I will fill out all of the requested information in this form.

[Bnyro]

Adding localization to the parser would be quite complicated, so I currently don't plan to do so.

[mgw2013]

Fair. How about an Option in settings?

[Bnyro]

Fair. How about an Option in settings?

That's the same difficulty. We use Comma inside method calls, e.g. log(3,5). If 3,5 could also be interpreted as a number, that would make things very difficult, so we would need to handle a lot of edge cases in each method call.

[mgw2013]

Fair again. So you would be forced to switch to ; (eg) for the method calls... maybe have a look at cutecalc's code?

-------- Ursprüngliche Nachricht -------- Von: Bnyro ***@***.***> Gesendet: 25. Oktober 2025 12:26:39 OESZ An: you-apps/CalcYou ***@***.***> CC: mgw2013 ***@***.***>, Author ***@***.***> Betreff: Re: [you-apps/CalcYou] Not following system number formatting (Issue #80) Bnyro left a comment (you-apps/CalcYou#80)

Fair. How about an Option in settings?

That's the same difficulty. We use Comma inside method calls, e.g. log(3,5). If 3,5 could also be interpreted as a number, that would make things very difficult.

…

-- Reply to this email directly or view it on GitHub: #80 (comment) You are receiving this because you authored the thread. Message ID: ***@***.***> Mit freundlichen Grüßen Michael Weigelt

[Bnyro]

Fair again. So you would be forced to switch to ; (eg) for the method calls?

Using ; perhaps would be the best option, yes. However, it's possible that there are languages that use ; instead of comma (I've really no idea about other language's conventions), so we should look at what other languages use as separator before implementing that. If we don't find any further conflicts, it should be possible to implement.

maybe have a look at cutecalc's code

That likely won't help, the parser logics have nothing in common as they use different approaches for parsing.

[mgw2013]

You may want to refer to <https://en.wikipedia.org/wiki/Decimal_separator> I'm not aware of any formatting using a semicolon as thousands separator or decimal mark.

-------- Ursprüngliche Nachricht -------- Von: Bnyro ***@***.***> Gesendet: 25. Oktober 2025 14:28:57 OESZ An: you-apps/CalcYou ***@***.***> CC: mgw2013 ***@***.***>, Author ***@***.***> Betreff: Re: [you-apps/CalcYou] Not following system number formatting (Issue #80) Bnyro left a comment (you-apps/CalcYou#80)

Fair again. So you would be forced to switch to ; (eg) for the method calls?

Using `;` perhaps would be the best option, yes. However, it's possible that there are languages that use `;` instead of comma (I've really no idea about other language's conventions), so we should look at what other languages use as separator before implementing that. If we don't find any further conflicts, it should be possible to implement.

maybe have a look at cutecalc's code

That likely won't help, the parser logics have nothing in common as they use different approaches for parsing.

…

-- Reply to this email directly or view it on GitHub: #80 (comment) You are receiving this because you authored the thread. Message ID: ***@***.***> Mit freundlichen Grüßen Michael Weigelt

[Bnyro]

The decimal formatter is localized now with 3a0dab7.

Turns out that we already had the most important code for it, so only few changes were needed.

Example: 1000000 should be displayed 1{required blank}000{required blank}000 as used in international formats or observe system language setting, e.g. German => 1.000.000

This still remains impossible with the current way our parser works, so we can keep it open for external contributors to create a pull request for it, but I won't work on that.