I'm currently evaluating the latest version of Activiti (5.1) and I was wondering how to handle i18n within forms; in particular, through build-in form rendering and using current Locale ? If possible, could you provide a simple example ? If it is not, could you give some hints to handle this requirement ?
Currently, nothing is built in into the default form rendering for this purpose yet… So you can't just use the explorer out of the box.
We allow you to plug in your own form-rendering engine (property ProcessEngineConfiguration.customFormEngines in config) which could handle this. Explorer uses the default form rendering, so you would have to override the default form-rendering engine with the one you use (overriding initFormEngines() on ProcessEngineCOnfiguration).
Explorer is 18n, but if you want the same for forms it will need to be yourself. Ie using a key in the form and doing a lookup in form code. That's quite a bit of customization work…