Camunda-modeler: Internationalize BPMN diagrams (i18n)

[StephenOTT]

_Updated Description (based on discussion below)_

Is it possible to internationalize BPMN diagrams with the modeler similar to this example?

---

Referenced in SUPPORT-5422

[nikku]

How would you like it to be used? It is part of the current Camunda Modeler, yes.

[StephenOTT]

@nikku how do you switch languages in the Modeler? Assume you already have the .properties files in same folder as bpmn file, with mimicking setup of: https://github.com/camunda/camunda-consulting/tree/master/snippets/i18n-process-model

Is there a variable to set?

[StephenOTT]

@nikku pref use case is ability to add translations directly in Modeler and those translations export to properties file and allow user to switch languages in modeler. But most basic usage would be to have properties files and the ability to switch lang in modeler. Translations would still have to be made directly in properties files.

[nikku]

Some misunderstanding here, let me try to clarify...

bpmn-js provides basic i18n features for diagram controls. The example you referenced provides internationalization for diagrams. Both are _not yet_ functionally integrated into the Modeler, yet.

From what I understand you'd like to have internationalization of BPMN diagrams in the modeler?

It would be interesting to learn more about the stuff you'd like to achieve and how you think I18N in the modeler would help you doing that.

[StephenOTT]

@nikku for I18n support what I am looking to do is be able to translate/internationalize a bpmn so it can be read in different languages (English, French, spinach, etc). In many cases it is a multi-language working environment and having the ability to read the bpmn in the language you understand best it very helpful.

[nikku]

All right, I updated the issue title and description accordingly.

This is something we may or may not have in the future.

[StephenOTT]

Is this something that could be added/you would accept through PR? Any thoughts on implementation preferences?

[nikku]

Yes, this is something we accept as a PR.

Some notes on feature / implementation:

• localizations should reside next to diagrams (same folder)
• feature is non-intrusive; controls for selecting / changing the are added when localization files are present, only
• implementation is tested

Based on this we could see if we can make improvements beyond the linked example.

[slizenko]

Any progress with this issue?

We also need multi-language support for diagrams.
In our system user selects the language during log in - everything changes except WFs.

[nikku]

We do not plan to work on this topic any time soon.