How to translate form-js

[Ken-Scofield]

How to support Internationalization (i18n) ?

Environment

• Host (Browser/Node version), if applicable: [e.g. MS Edge 18, Chrome 69, Node 10 LTS]
• OS: [e.g. Windows 7]
• Library version: [e.g. 2.0.0]

[Ken-Scofield]

@Skaiir, @pinussilvestrus Can you provide a demo?

[Skaiir]

@Ken-Scofield fyi Niklas no longer maintains the project officially (though of course this is open source so he's still free to contribute :D).

So, depends if you want to internationalize the form-js or the form itself.

For form-js, we currently don't support internationalization. See https://github.com/bpmn-io/form-js/issues/1055 for discussions. We're also in the middle of a pretty large re-architecturing moving towards the next major so it's probably not the right time to start. But we have it in mind for the future. We would mimic how it is done in bpmn-js.

For the forms you can use some feel expressions to achieve this.

[itzhouze]

@Skaiir @nikku

We're also in the middle of a pretty large re-architecturing moving towards the next major so it's probably not the right time to start. But we have it in mind for the future. We would mimic how it is done in bpmn-js.

Hello everyone, we are also interested in a translation solution and are about to consider creating a fork of the form-js project in order to incorporate a translation logic.

This would of course make little sense if you are considering incorporating a translation solution at the form-js level and are also working on a re-architecturing.

Is there any news about the major restructuring and when it will be ready for use?