Language translation feature

[Jani Laakso]

See high level description from roadmap

[Jani Laakso]

Milestone 4.2.0-rc deleted

[Joonas Lehtinen]

Copied descr from the "roadmap" here:

What: Applications may be translated using tools provided within Toolkit. Translation may be performed by non technical people.

Why: Common requirement on enterprise applications. Reduces costs from customer if developers do not have to build own translation system.

Please could you argument how this would be better than doing the thing in IDE? Please reopen if needed.

[Jani Laakso]

Technical people (develoeprs) like to use Eclipse and it's "internationalization" features, but the big catch is that non technical people (translators) never use Eclipse. Translators also dislike doing full translation by massive xml / text file where context of the translatable id cannot be seen.

One possible better workflow could be the following:

Any Toolkit component (or even application) may be switched into "translation" mode. This adds an translation mechanism to the client side by following way:

• user clicks any Toolkit component with middle button
• user clicks any Toolkit component with left button + holding shift down

=> translation window is opened

Of course translator cannot be sure that every view and id was translated, but this is very convenient way to translate any application because with this workflow you see translatable id into it's real context. Next step is that translator translates the missing id's using some other mechanisms (typically text / xml file, but never Eclipse IDE).