# Perspective use of term in translation manager?

**URL:** <https://forum.inductiveautomation.com/t/perspective-use-of-term-in-translation-manager/41713>\
**Category:** Ignition\
**Tags:** perspective, ignition80\
**Created:** [December 22, 2020, 8:36am UTC](https://forum.inductiveautomation.com/t/perspective-use-of-term-in-translation-manager/41713 "2020-12-22T08:36:37Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\
**Post date:** [December 22, 2020, 8:36am UTC](https://forum.inductiveautomation.com/t/perspective-use-of-term-in-translation-manager/41713/1 "2020-12-22T08:36:37Z")

</div>

I try to translate some terms in perspective.

For example, with the **Table** component, how to translate **“Filter Table…”**?

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/8/e835e2a622742fab2311e55c6f8c75df1c38c4c9.png)

In the translation manager (with Ignore Capitalization settings) and Perspective project Locale set to “français”, “Filter Table…” is not subsitute with the term in the translation manager ?

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/6/f66b9a116494a4f3d802c7abffca129a684130ec.png)

---

<div class="post-metadata">

**Author:** ![fleclerc](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/fleclerc/32/20480_2.png) [@fleclerc](https://forum.inductiveautomation.com/u/fleclerc)\
**Post date:** [March 9, 2021, 7:33pm UTC](https://forum.inductiveautomation.com/t/perspective-use-of-term-in-translation-manager/41713/2 "2021-03-09T19:33:13Z")

</div>

I tried the same thing before looking for an answer. Looking forward for a better use of Translation Manager in Perspective.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [March 9, 2021, 7:54pm UTC](https://forum.inductiveautomation.com/t/perspective-use-of-term-in-translation-manager/41713/3 "2021-03-09T19:54:16Z")

</div>

It’s currently not possible to translate this string, although translation in Perspective is actively improving - for instance, 8.1.3 adds broad localization support to the alarm status and alarm journal table in Perspective.

---

<div class="post-metadata">

**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\
**Post date:** [March 9, 2021, 8:26pm UTC](https://forum.inductiveautomation.com/t/perspective-use-of-term-in-translation-manager/41713/4 "2021-03-09T20:26:28Z")

</div>

8.1.3 has improved a lot translation for alarms !  
Icing on the cake, would be some translation terms with a component scope like for vision, in order to have translated terms customisable for some components.

---

<div class="post-metadata">

**Author:** ![baisea2018](https://avatars.discourse-cdn.com/v4/letter/b/5daacb/32.png) [@baisea2018](https://forum.inductiveautomation.com/u/baisea2018)\
**Post date:** [March 10, 2021, 2:01am UTC](https://forum.inductiveautomation.com/t/perspective-use-of-term-in-translation-manager/41713/5 "2021-03-10T02:01:37Z")

</div>

hello, I’ve upgrade my ignition to 8.1.3. The problem is that the translation manager works so good in the designer while I lauch it to the web page, the language remains untranslated, would you please help me in this issue? Thank you so much!!

---

<div class="post-metadata">

**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\
**Post date:** [March 10, 2021, 6:47am UTC](https://forum.inductiveautomation.com/t/perspective-use-of-term-in-translation-manager/41713/6 "2021-03-10T06:47:59Z")

</div>

The translation is based on the locale of the session (or browser). If you want the browser session to translate, then the locale of the session needs to be set to a locale for which you have translations in place. If you have a locale of `en-US` in the browser, and you have translations in place for Esperanto, then you need to either change the default locale of the browser in the browser settings, or you need to set `session.props.locale` to “eo” in order for it to begin translating the content based on your translations.

---

<div class="post-metadata">

**Author:** ![baisea2018](https://avatars.discourse-cdn.com/v4/letter/b/5daacb/32.png) [@baisea2018](https://forum.inductiveautomation.com/u/baisea2018)\
**Post date:** [March 10, 2021, 1:06pm UTC](https://forum.inductiveautomation.com/t/perspective-use-of-term-in-translation-manager/41713/7 "2021-03-10T13:06:26Z")

</div>

I’ve already set ‘session.props.locale’ to the language I want and it actually worked in the designer. But in google browser, the content reminded English. Is it that I need to set the language of my google browser to what I want ?

---

<div class="post-metadata">

**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\
**Post date:** [March 10, 2021, 4:51pm UTC](https://forum.inductiveautomation.com/t/perspective-use-of-term-in-translation-manager/41713/8 "2021-03-10T16:51:32Z")

</div>

Setting `session.props.locale` in the Designer does not set the locale of running sessions on start because that setting is set at the project level:

![Screen Shot 2021-03-10 at 8.48.12AM](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/7/a74e0177c455566178ddb6244c0961b97cab48c0.png)

The `session.props.locale` property allows for _changing_ the locale at runtime. So you have three options:

1. Change the project-wide setting to force all sessions to open as a certain locale.
2. Change your browser to the locale you want to use.
3. Allow for sessions to set their own locale by supplying some sort of input (Dropdown is common) which is bidirectionally bound to the `session.props.locale` property.
