As far as I know, there are no concrete plans of supporting multi-language parameters, although I'm sure it's been asked a few times.
Here in Switzerland we have a lot of the same issues with our several official languages that we are required to support. For us, the solution has been to use a custom web (GUI) interface to the FME Server REST API. It is a bit of an up-front development, but fortunately it is possible to make it pretty dynamic, e.g. you can query FME Server for a list of all published parameters on a specific workspace and build the entry form based on that. If you standardize the parameter names, you can also save a lot on translation.
As far as I know, there are no concrete plans of supporting multi-language parameters, although I'm sure it's been asked a few times.
Here in Switzerland we have a lot of the same issues with our several official languages that we are required to support. For us, the solution has been to use a custom web (GUI) interface to the FME Server REST API. It is a bit of an up-front development, but fortunately it is possible to make it pretty dynamic, e.g. you can query FME Server for a list of all published parameters on a specific workspace and build the entry form based on that. If you standardize the parameter names, you can also save a lot on translation.
Thanks for your answer. We are looking to keep the web interface as simple as possible. We would have prefer FME Server to offer i18n fonctionality at the workspace level.