« [Movie] Custom Controller | Main | [Movie] Using Style Sheets in Servoy »

October 04, 2004

[Tip] i18n dual purpose

by Marcel Trapman
www.it2be.com

Since version 2.1 the Servoy Team blessed their RAD tool with internationalization (i + 18 characters + n).

Because I work with Servoy since version 1.2 internationalization was/is completely new to me. But, I want to sell my solution internationally so this is a must for. Therefore I recently started to really convert all labels, dialogs etc into an i18n value.

My experience: the bigger the solution the more work. And when I say work I really mean WORK...

My advice therefore is short: When you consider or dream of selling your solution outside your language area you should work with i18n from the start. It will take a little time extra to start with but will be a huge timesaver later on.

But, there can be another reason. Let's assume your solution has 20 forms with 'OK' buttons. After a while your users ask you to change that text into 'Yes'. Without i18n this would mean that you have to search for all forms holding that button and change all individual button text properties. With a lot of forms this can take a lot of time. With i18n this will only take you seconds.

Sound like a great bonus huh..

Cheers

Posted by IT2Be on October 4, 2004 at 03:39 PM in Tips | Permalink

TrackBack

TrackBack URL for this entry:
https://www.typepad.com/services/trackback/6a00d8341c8d8153ef01bb096945bf970d

Listed below are links to weblogs that reference [Tip] i18n dual purpose:

Comments

Damn, the "OK" button example hadn't occurred to me. Another option for GUI abstraction. Good tip!

Posted by: David Workman | Oct 4, 2004 6:40:44 PM

Great tip! Here's another tip when using i18n:

MAKE SURE you have set up a "default i18n server" and "default i18n table" in the "preferences" BEFORE you try to import i18n data.

If you don't, you won't be able to import i18n data.

That should save you about 10 hours of trial and error... :-)

Posted by: Bob Cusick | Oct 5, 2004 8:48:15 PM

The comments to this entry are closed.