Skip to content
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

Number formatting pattern #68

Open
kaoecoito opened this issue Aug 15, 2020 · 0 comments
Open

Number formatting pattern #68

kaoecoito opened this issue Aug 15, 2020 · 0 comments

Comments

@kaoecoito
Copy link

Hi,

Some time ago I identified that Axelor only works with locales without the variant as (pt, en) and not (en_us, pt_br), I even suggested changes about it because Brazilian Portuguese is different from Portuguese used in Europe (Portugual) .

After studying the code and doing tests I was able to implement language modifications without needing this change, I simply created a personalized module with a messages_pt.csv with only the words that are meaningless in Brazil, this allows me to use in Brazil without users being in doubt of the meaning.

However, I noticed another effect of using locales only with the language prefix and not with the variant. Values ​​are shown with the thousands separator (,) and decimal (.), While in Brazil the thousands separator is (.) And the decimal a (,).
A suggestion that would perhaps simplify this without causing changes in the way the locale is created would be the number formatting to be loaded from the configuration, the same is done with the date formation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant