[IGN-11921] Translation works differently from prior versions

Ignition 8.3 Early Access
1

Hi all,
I believe the translation system is behaving differently from 8.1 for Sepasoft components.
New:
No value for the target language (or don't translate), and no value for English (Alternative). Need to have a key for the phrase in the tranlation manager.
Then the value is blank in the browser.
Old:
No value for the target language, and no value for English (Alternative).
Then the original English value is shown in the browser.

This seems to be true of Sepasoft components, but not of native Ignition components. Is this a new behaior that we need to adjust Sepasoft components for, or is it a defect? Thanks.

2

Could we get more context? Is this within Perspective or within the Gateway?

1 Like
3

This is happening in Perspective and seems related to the way the import is working - when an empty string is entered in the translation manager it does not create an entry in data\config\core\ignition\translations\en.json so no translation is applied, when importing it is creating blank string entries for the terms
I83M40_en.PROPERTIES (8.0 KB)

Example of a snippit from the en.json

{
  "(No Data)": "",
  "*Please confirm a downtime reason override.": "",
  "1234": "",
  "<None>": "",
  "<Select One>": "",
  "<back": "",
  "Abort Operation": "",
  "Activate": "",
  "Active Time": "",
  "Actual Quantity": "",
  "ActualBegin": "",
  "ActualEnd": "",
  "Add": "",
  "Add Area": "",
  "Add New Work Order": "",
1 Like
4

:grinning: Okay. Good information. I'll pass it along.

2 Likes
5

You are correct. It's expected that a key without a value would store as a null not an empty string. A bug ticket has been created to fix this.

2 Likes
6

We migrate from 8.1.49 to 8.3.0, 8.3.1 and now 8.3.2

All terms with space have been replaced with lowercase without space but doesn't translate.
If I try to fix them, for example :

  "Display Path": "Equipement",

in the translation file:

C:\Program Files\Inductive Automation\Ignition\data\config\resources\core\ignition\translations

those terms are still not translated.

Is there a known bug or I missed something ?

My settings are:
session.propos.locale = fr

{
  "scope": "A",
  "version": 1,
  "restricted": false,
  "overridable": true,
  "files": [
    "fr.json",
    "en.json"
  ],
  "attributes": {
    "lastModification": {
      "actor": "unknown",
      "timestamp": "2025-12-04T13:12:13Z"
    },
    "ignorePunctuation": true,
    "caseInsensitive": true,
    "lastModificationSignature": "cb83c7afdaae82d4cd66c3b9e900d6e808cbda65efc5ffbd342af2476a83da4c",
    "ignoreWhitespace": true,
    "ignoreTags": true
  }
}
1 Like
7

Hm, at first when I tried things were working fine, then I started getting weird behaviors.

To be clear - are you experiencing issues only with Perspective components' "built-in" translation (e.g. a label with a value of Display Path not/incorrectly translating), or are you also having issues with the translate expression function/scripting function(s)?

8

I solved the issue with help of support.
I have replace the ressource file and rescan from the gateway. I added some term for ass data displayed on alarms components.
Built in term with space or them are fine.

I will repoen the ticket.or the forum post if the issue come back

2 Likes