Skip to main content
Solved

Is there anyway to publish parameters in more than a single language?

J

Hi,

We are building a data extraction tool based on FME Server. This application build a form dynamically based on the published parameters. It needs to work in french and in english. Since i18n isn't possible on parameters descriptions and alias, we need to rely on a custom format that we put in the descriptions. The application has an additionnal step of parsing the descriptions to get the french or the english names/descriptions depending on the current language of the user.

Is there any plan to support i18n on parameter names and descriptions?

Is there a different way to manage that then the one we use?

Thanks!

Best answer by david_r

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.

View original
Did this help you find an answer to your question?

2 replies

david_r
Evangelist
  • david_rEvangelist
  • Best Answer
  • May 28, 2017

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.

J
david_r wrote:

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.

 

 

Reply


Helpful Members This Week

Community Stats

31,040
Posts
117,664
Replies
38,818
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.