# Problems with language translations

**URL:** <https://forum.inductiveautomation.com/t/problems-with-language-translations/111618>\
**Category:** Ignition\
**Tags:** perspective, ignition83\
**Created:** [October 21, 2025, 2:52pm UTC](https://forum.inductiveautomation.com/t/problems-with-language-translations/111618 "2025-10-21T14:52:58Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [October 23, 2025, 4:17pm UTC](https://forum.inductiveautomation.com/t/problems-with-language-translations/111618/5 "2025-10-23T16:17:20Z")

</div>

Perhaps the underscores versus dashes issue, as noted here:

> [@Concatenation in string translation](https://forum.inductiveautomation.com/t/concatenation-in-string-translation/111669/11):
>
> This works but now another problem arises: if I use the function "translate('somekey', {session.props.locale})", the "session.props.locale" property must be, for example, "en\_US" while if I use the function "translate('somekey') the "session.props.locale" property must be "en-US" (this format, the other function, gives me an error saying: "Invalid locale format: en-US"). Depending on which one I use, I see the translations of certain texts working or not. Why is this? This is all quite funny …

---

_[View the full topic](https://forum.inductiveautomation.com/t/problems-with-language-translations/111618)._