>> In first the artifacts listed below have some messages/labels that
>> should be in the message.properties file translation entries, for
>> example:
>>
>> 1) The method
>> ca.sqlpower.architect.swingui.CompareDMPanel.getStartabilityStatus()
Fixed! I put in keys for the words "older" and "newer" and then made
two messages that use them in a {0} substution.
>> 2)ca.sqlpower.architect.SQLDatabase.getName()
I've externalized all the messages in SQLDatabase that are likely to
become user-visible. However, SQLDatabase has moved to the
sqlpower-library project (also on Google Code Hosting). When we moved
it to the sqlpower-library, we also changed its package name to
ca.sqlpower.sqlobject.
The new version of SQLDatabase with externalized strings is in
sqlpower-library r837.
>> 3) ca.sqlpower.architect.swingui.ArchitectFrame.buildOLAPEditMenu()
Done!
>> 4)
>> ca.sqlpower.architect.swingui.RelationshipEditPanel.RelationshipEditPanel
>> (ArchitectSwingSession)
Done!
Fixes for items 1, 3, and 4 are in power-architect r2957.
>> After, the swing standard components have yours messages/labels in
>> enliglish for latin-1 jvm, or default instalation, thus, will be
>> necessary translate these components too. A idea that like to do this,
>> I found in http://beradrian.wordpress.com/tag/i18n/, where it's
>> possible make it.
Great pointer! I have not done this yet, but it's something we should
do. I've bookmarked the page.
>> Now the question is: Probably the effort to I18N the Power*Architect
>> to be greater than I imagine in the begin. Do we go ahead? Can this
>> decision delay the Power*Architect development plans?
Hopefully not... I've already fixed most of what you pointed out. With
your itemized list of problems, it was easy to fix.
Thanks for all your help.
-Jonathan