You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m using UA ModelCompiler for C# and need to include descriptions with multiple language options in my design .xml file. However, I encountered issues where the generated .xml does not properly include Locale attributes, leading to missing translations.
I found a previous GitHub issue (https://github.com/OPCFoundati…../issues/95) where this problem was reported, and a contributor mentioned that “Specifying a locale is a missing feature in the ModelDesign schema” and that they would investigate adding it. This was reported in 2021, but the issue is still open.
My Questions:
Has support for specifying Locale in Descriptions been added to the latest Dotnet UA ModelCompiler?
If not, is there a recommended workaround to ensure multi-language descriptions are correctly included in the generated .xml?
Is there an official way to use external translation resources or link translations via the Key attribute, as mentioned in the UA Model Design.xsd? I’ve got a version working where I override the custom node manager 2’s read method to add some localisation logic, but that seems like a lot of effort for something that should be part of the model building process already.
I appreciate any updates or guidance on this!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
I’m using UA ModelCompiler for C# and need to include descriptions with multiple language options in my design .xml file. However, I encountered issues where the generated .xml does not properly include Locale attributes, leading to missing translations.
I found a previous GitHub issue (https://github.com/OPCFoundati…../issues/95) where this problem was reported, and a contributor mentioned that “Specifying a locale is a missing feature in the ModelDesign schema” and that they would investigate adding it. This was reported in 2021, but the issue is still open.
My Questions:
Has support for specifying Locale in Descriptions been added to the latest Dotnet UA ModelCompiler?
If not, is there a recommended workaround to ensure multi-language descriptions are correctly included in the generated .xml?
Is there an official way to use external translation resources or link translations via the Key attribute, as mentioned in the UA Model Design.xsd? I’ve got a version working where I override the custom node manager 2’s read method to add some localisation logic, but that seems like a lot of effort for something that should be part of the model building process already.
I appreciate any updates or guidance on this!
Thanks,
John
Beta Was this translation helpful? Give feedback.
All reactions