Internationalisation

Igor Couto igor at pixelmedia.com.au
Sat Jan 4 06:44:01 EST 2003


Dear Revolutionaries,

I've read the (rather clever and useful) recommendation that all text 
(string) that is to be displayed to a user, anywhere in the interface, 
should be kept on a separate text file, so that this file can be easily 
sent to translators. This not only makes the translator's job easier 
and faster (and cheaper), but also means they can translate without 
having to gain direct access to your stacks.

My question is: what is the procedure for 'loading' all the text ONTO 
the interface? How does one change all the text on menus, buttons, 
label fields, etc?

In the Revolution documentation, they mention the use of custom 
property sets as a way to 'store' internationalisation information - 
ie., you store all the different strings needed for a certain language 
in a custom property set for that language. At launch time, we would 
only have to 'load' the appropriate set.

Where I'm getting confused is with the 'normal' (ie, NOT custom) 
properties - ie, the names/labels of buttons, or text of label fields. 
What do we do with these? How can we change *these* as well when we 
change the property set?

Or have people found other ways/approaches to internationalising their 
apps?

All suggestions GREATLY appreciated!

Many thanks, and

Kind Regards,

--
Igor de Oliveira Couto
----------------------------------
igor at pixelmedia.com.au
----------------------------------




More information about the use-livecode mailing list