Thanks Tim for this proposal. I like the way it's done. I have two minor questions: - Will it be possible to change the language without to have to reload the page ? - The GeoExt translation framework will have to coexist with the OpenLayers or ExtJS translation framework. Do you see any issue with that ? Thanks, Cédric
On Thu, Nov 18, 2010 at 1:14 AM, Tim Schaub <[email protected]> wrote: > Hey- > > I've attached a patch for a simple i18n framework to #352. > > http://trac.geoext.org/ticket/352#comment:3 > > As mentioned in the comment, the objective was to achieve a few goals: > > 1. Support runtime preferences where possible (browser language > settings), allowing a single build to include translations for multiple > languages. > > 2. Make language files as simple as possible for translators to work with. > > 3. Allow applications (or the library in the future) to support setting > the language after initialization (or initial library load). > > I'm interested to hear feedback. > > Tim > > -- > Tim Schaub > OpenGeo - http://opengeo.org > Expert service straight from the developers. > _______________________________________________ > Dev mailing list > [email protected] > http://www.geoext.org/cgi-bin/mailman/listinfo/dev > -- Welcome to my world: http://www.cedricmoullet.com/ My Linked In profile: http://www.linkedin.com/in/cedricmoullet Twitter: http://twitter.com/cedricmoullet Home sweet home: http://map.geo.admin.ch/?crosshair=bowl&zoom=11&X=185241.24219&Y=561288.90625&bgOpacity=0&selectedNode=node_ch.swisstopo.fixpunkte-lage1
_______________________________________________ Dev mailing list [email protected] http://www.geoext.org/cgi-bin/mailman/listinfo/dev
