i18n - 'Best Practice' for Development?

Classic Servoy
1

I’ll need to include i18n in my app. Questions is - which is the ‘best practice’ development method:

a. Add i18n data tags as each form is finalised OR

b. Develop the entire app and then reconsider each entry to create the i18n entries / tags etc?

I’m sure both techniques have their merits but would value feedback from real world development - and developers who have used either / or / both?

Feedback would be much appreciated Folks

Cheers

2

I, as many others, have been working with Servoy from the pre-I18N-days.

I18N is great, and is not only helpful for lanquage support but also to support quick global changes in the wording of buttons etc.

It really takes a lot of time (too much imho) to change it afterwards. If I were you I would use I18N right from the start.

3

You could even ‘label’ your dataproviders within the tabledefinitions.
Goto dataproviders, click on properties of a column you want to label.
Enter your i18n key in the ‘title’ property ( should be something like: i18n:<i18n_label> )

When placing your dataproviders on the form, Servoy will automatically include this i18n label.
This could be usefull if you’re gonna use your dataproviders more than once.

4

mboegem:
You could even ‘label’ your dataproviders within the tabledefinitions.
Goto dataproviders, click on properties of a column you want to label.
Enter your i18n key in the ‘title’ property ( should be something like: i18n:<i18n_label> )

When placing your dataproviders on the form, Servoy will automatically include this i18n label.
This could be usefull if you’re gonna use your dataproviders more than once.

Very neat Marc - thanks for that feedback!

I’ll use that A LOT :D