Multilingual support for plugin

Planned

Phạm Quang Đăng

July 27, 2026 03:20 Edited

- In the local settings, the VMS supports many languages for different nations. I'm trying to make my plugin have the language selection option in engineSettingsModel.
My method was having a selection box in Engine Settings ( which is located in Site Administration → Integrations → [select my plugin] ). I did so by dynamically load different manifests for both engine and device_agent. The method works but it cause the detected and recorded object to not show up on Advanced Object Search whenever server reset, crash, ect… happens. 
- I have read the SDK thoroughly and haven't found any support method for multilingual, or syncronizing the local language setting to the plugin. As the plugin has been uploaded i would love to have it accessible to all other languages currently available.

- Have anyone done this before ? Can you share some knowledge ? My desired outcome is when selecting the prefered language in Local Settings or plugin settings, every text that is visible to the user should be change accordingly. This means plugin settings in [Site Administration], plugin settings in [Camera Settings], attribute name and text in Advanced Object Search, plugin action name, etc…

My workspace: Witness 6.1.2.42921, plugin build on SDKs from version 6.0.1 and above.

2

• 

  Ichiro

  • Network Optix team

  July 29, 2026 05:55 Edited

  Hi Phạm Quang Đăng
  
  Developers can build multi-language (i18n) plugins for Nx. However, the scope is inside your plugin only.

  That said, in the current desktop client architecture, there might have had no mechanism for passing locale information between the 3rd-party plugin and the desktop client, so a plugin currently can't automatically follow the desktop client's language setting. This was raised and but there's been no implemetation it so far.

  In the meantime, the workaround is for developers to add a language selector inside the plugin itself, letting users choose their preferred language directly. (inside your plugin and the interface that generates by your plugins)

  0
• 

  Phạm Quang Đăng

  July 29, 2026 08:49

  Thank you for replying, Ichiro. Actually i am doing exactly what you are telling while waiting for answer. It is a bit tricky to get the manifest strings to work without breaking the model. Thank you for giving advices

  0
• 

  Phạm Quang Đăng

  July 30, 2026 04:55 Edited

  i forgot to mention, i managed to put the language selector in engine settings and update texts that are visible to the user in engineSettingsModel and deviceAgentSettingsModel. The only downside is it can break how Advanced Object Search finds and/or loads detected objects in Nx since the field “name” and “attribute” in typeLibrary and supportedTypes also changes, which may not following the attribute and manifest guidelines. Integration manifest can not change language due to the nature of how a plugin was initialized.

  1

Please sign in to leave a comment.