Translation of Asset Name

Manager UI
1

Dears,
please advise -
is there any way to translate asset type name, e.g. Light Asset?
and is there any way to change (and/or translate) by default name of an asset?

image
image1488Ă—833 42.2 KB

2

just to add to above, same question related to attribute naming. can it be translated?

image
image1118Ă—668 39.1 KB

3

Hi!

No, I believe this is not possible.
The labels and names are configurable, but not for individual languages.

Let me ping @Pierre and @Don to make sure.

5

Thanks for letting me know.
could you please also check - search field and location icons are on top of attribute list in the history panel, tried to find where to correct myself but couldnt.

image
image1766Ă—692 100 KB

6

Thanks for reporting!
I’ve made an GitHub issue, so maybe it will get picked up one day.

However, this issue seems only present with “very wide screens”,
where the menu goes up instead of downwards like normal.
Or you have a longer list of attributes, like you do.

7

Hi @RRR ,

Yes it’s possible to translate attribute names like this in the or.json (or translation files of your custom app) of the language you want to use:

  "label": {
    "attribute": {
      "YourAssetType": {
        "attributeName": "Translation of attribute name",

Translating asset names is not possible though.

Kind regards,

Don

8

hi Don,
thanks for a hint, above worked for me,
as well as below (in or.json):

“label”: {
“asset”: {
“ElectricityProducerSolarAsset”: “PV solar asset”,
“ElectricityProducerWindAsset”: “Wind turbine asset”
},

1 Like
9

Oh wow, thanks for sharing!

Maybe should document this somewhere @Don

10

in addition to above.
changes in the file or-add-asset-dialog.ts

// public name: string = "New Asset";
public name: string = i18next.t("new_asset");

and adding into file or.json

“new_asset”: “New asset”

allowed me to have a translation of a default “New asset”.
hope it doesnt break any other functionality

11

Hi!

No that wouldn’t break any existing functionality.
It doesn’t do any harm haha

Actually, feel free to open a PR on our GitHub if you’d like.
Doesn’t hurt to merge enhancements like this for the community :+1:
We would really appreciate it!