[BUG-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?

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": "",
4

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

1 Like
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.

1 Like