Would it be better to see if we can get a volunteer translator for each language we want to support in OpenJUMP and coordinate with them to maintain the properties files for each language when new entries are made?
I wonder if this system would be better than "half-supported" languages in OpenJUMP. I can see if my best friend could help me with the Spanish file. The Sunburned Surveyor On 8/16/07, Michaël Michaud <[EMAIL PROTECTED]> wrote: > I can tell you what Stefan answered to me after I asked the same question : > > add the key and the english value in every file and replace the value by > an appropriate translation where you can > > As I modified I18N original code, I can add that the normal behaviour of > jump should be : > - if a key in a specific language file is not found, jump should use the > one in jump.properties > - if the key does not exist in any file, OpenJUMP should use the last > part of the key (after a split(".")) as the string value > > Michaël > > Paul Austin a écrit : > > >What's the policy related to adding new I18N entries to the properties > >file. Do I just add the entries with the English to each file and hope > >that someone does a translation at some point? > > > >Paul > > > >------------------------------------------------------------------------- > >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