# \[BUG\] Decimal separator in numeric input field behaves wrong for non-english locales

**URL:** <https://forum.inductiveautomation.com/t/bug-decimal-separator-in-numeric-input-field-behaves-wrong-for-non-english-locales/23361>\
**Category:** Ignition Early Access\
**Created:** [March 14, 2019, 8:04pm UTC](https://forum.inductiveautomation.com/t/bug-decimal-separator-in-numeric-input-field-behaves-wrong-for-non-english-locales/23361 "2019-03-14T20:04:43Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Sanderd17](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/sanderd17/32/8735_2.png) [@Sanderd17](https://forum.inductiveautomation.com/u/Sanderd17)\
**Post date:** [April 3, 2019, 6:56am UTC](https://forum.inductiveautomation.com/t/bug-decimal-separator-in-numeric-input-field-behaves-wrong-for-non-english-locales/23361/3 "2019-04-03T06:56:14Z")

</div>

There have been issues with decimal separators on foreign languages before. See

> [@NumericTextField Decimal format](http://forum.inductiveautomation.com/t/numerictextfield-decimal-format/9907):
>
> In our country we have Decimal separator ‘,’ and ‘.’ for the thousands. When i use numerictextfield component with a float value, it show value like ‘12.88’ and I must enter ‘12,88’ for a valid change value otherwise it understand ‘1288’ Is it a way to standardize display and input value with the numerictextfield?

But this appears to interpret the separator one stage further. First rendering it with one separator, and then interpreting it as the other.

---

_[View the full topic](https://forum.inductiveautomation.com/t/bug-decimal-separator-in-numeric-input-field-behaves-wrong-for-non-english-locales/23361)._