Just to add to Dave's explanation, I would like to recommend the use of 
ResourceBundleEditor <http://sourceforge.net/projects/eclipse-rbe> 
plugin for eclipse when creating a new UI translation.

It allows to work on various languages at a time and to quickly locate 
any missing resource, at the cost of leaving it take control of the 
.properties file organization, which is a price I'm glad to pay after 
having translated the whole udig 1.1 resources some years ago (that is, 
the resources inside the file may end up in a different order than in 
the english one).

Cheers,
Gabriel

David Winslow wrote:
> In the source tree (mostly under src/web/, but in any module that
> contributes Wicket pages.  Please don't forget the GeoSearch module ;) )
> each module's src/main/java/ directory contains a file called
> GeoServerApplication.properties.  These files contain the
> English/default translations for the i18n'ized strings in the UI.  Other
> languages can be added by copying the files and suffixing an underscore
> and the language code to the main part of the filename (ie, the de
> translation lives in a set of GeoServerApplication_de.properties files.)
> 
> The translations should preserve the keys exactly (everything before the
> = sign; case-sensitive) and replace the English text on each line with
> the translation.  Translations can include positional parameters; these
> are identified by number starting at zero.  So, if we are translating a
> phrase that talks about some table, like this:
> foo.bar.tablename=The table's name is {0}
> 
> then the corresponding Spanish translation might (please don't hurt me,
> native speakers!) go like this:
> foo.bar.tablename={0} es el nombre de la tabla.
> 
> These parameters do not have to appear in the same order in different
> translations.
> 
> Hope this helps.
> 
> --
> David Winslow
> OpenGeo - http://opengeo.org/
> 
> On Mon, 2009-08-10 at 18:06 -0400, Mike Pumphrey wrote:
>> In 1.7.x, we have a number of different languages set up in the UI.  It 
>> sounds like we don't have the same for 2.0.x.  Is this true?  How does one 
>> create a new language pack for 2.0?  If there are no instructions yet, I'm 
>> happy to write them.
>>
>>
>> Thanks,
>> Mike Pumphrey
>> OpenGeo - http://opengeo.org
>>
>> ------------------------------------------------------------------------------
>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
>> trial. Simplify your report design, integration and deployment - and focus 
>> on 
>> what you do best, core application coding. Discover what's new with 
>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>> _______________________________________________
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
> 
> 
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> trial. Simplify your report design, integration and deployment - and focus on 
> what you do best, core application coding. Discover what's new with 
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to