i18n and Transition

Classic Servoy
1

Here’s our scenario…

We are in the middle of migrating our solution to Servoy 4.0.

We have a saas solution with customers using 3.5.7.

We have a new request that a customer needs to have a French language option.

  1. Is there a way to give access to the i18n table in servoy so the customer can do the french transactions for us… without seeing and modifying anything else in our solution?

  2. Will there be issues if we’ve updating our i18n tables in 3.5.7 and we’ve already migrated our next version of our app to 4.0?

Do I make any sense? :)

Chico

2

You could build a form based on the i18n table and let them translate the keys.

You can also just give them an export of the unique keys in the base language (english?), have them translate it and then import the french version into the i18n table.

Since i18n keys are just records in a table in the database, it’s quite easy to make an extract and import again.

The same applies moving from 3.5 to 4: i18n keys are just a table.

Paul

3

pbakker:
You could build a form based on the i18n table and let them translate the keys.

Why reinvent the wheel? ;)

http://www.servoyforge.net/index.lasso?go=polyglot