l10n and the ability to translate the gui

added support for localization in a manner congruent with java's resourcebundle mechanism and similar in design to the model-metadata properties file.

for a given application, define a resource bundle for a given locale, with base name "localed-metadata".

see the default-generated sample file:

locale-metadata_fr.properties

for an example.

then, assuming your default locale matches the resource bundle file you created, you should see that field names, commands, and type names obey your specifications.

here are example localized properties (using french as an example):

# Application-Specific Localization Example Entries # =================================================

#Speaker=Presenteur #Speakers=Presenteurs #Speaker.name=Nom #Speaker.title=Titre #Speaker.bio=Biographie #Speaker.photo=Photo #Speaker.AddTalk?=Ajoute Une Presentation #Speaker.contact.homePhone=Telephone Maison

# JMatter Global Localization Entries # ===================================

AbstractComplexEObject.Save=Sauve AbstractComplexEObject.Cancel=Abandone AbstractComplexEObject.Copy=Copie AbstractComplexEObject.Paste=Colle AbstractComplexEObject.SaveAndClose?=Sauve et Ferme AbstractComplexEObject.Open=Ouvre AbstractComplexEObject.Edit=Edite AbstractComplexEObject.Delete=Efface AbstractComplexEObject.Refresh=Rafraichi

ComplexType?.New=Fait Nouveau ComplexType?.Browse=Liste ComplexType?.Find=Trouve

enjoy. also, report any issues please.

thanks, eitan

ps: corresponding svn revision #: 73