Landon, The I18N class in Jump only works for items in the core as it only loads information from the language/jump_xx.properties file in the core.
Have a look at that code to see how things work. We should extend it so that there can be different I18N instances for different plug-ins. Paul Sunburned Surveyor wrote: > Hmmmm. Actually the first way seemed simpler, if I remember correctly. > > If we use the first way in the core, that is the way I would like to > learn, so I can help with I18N in the core if it is ever needed. > > Can you confirm that we use the first method in the core? > > Thanks, > > The Sunburned Surveyor > > On 10/17/07, Stefan Steiniger <[EMAIL PROTECTED]> wrote: > >> I myself used only the i18n class, but if i remember correctly the other >> method is used by the pirol people. >> >> as it is a plugin, you may try the second approach (may be it is better >> for plugins .. not sure about that) >> >> stefan >> >> Sunburned Surveyor schrieb: >> >>> The OpenJUMP wiki mentions two (2) ways that a plug-in can be >>> internationalized. The first way uses the I18NPlug.java class. The >>> second way was suggested by someone named "Holger", and involves the >>> use of ResourceBundle class. >>> >>> I'm getting ready to attempt my first internationalization of a >>> plug-in, and I was wondering what the advantages are of one way over >>> the other. Is there one that I should be using? Is there one everyone >>> else is using? >>> >>> Internationalization isn't my area of expertise (then again, I may not >>> have any areas of expertise) so I would appreciate any advice on this >>> matter. >>> >>> I thought I would ask before I committed to one of the two methods. >>> >>> Thanks, >>> >>> The Sunburned Surveyor >>> >>> ------------------------------------------------------------------------- >>> This SF.net email is sponsored by: Splunk Inc. >>> Still grepping through log files to find problems? Stop. >>> Now Search log events and configuration files using AJAX and a browser. >>> Download your FREE copy of Splunk now >> http://get.splunk.com/ >>> _______________________________________________ >>> Jump-pilot-devel mailing list >>> Jump-pilot-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >>> >>> >>> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> Jump-pilot-devel mailing list >> Jump-pilot-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >> >> > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
