O~h, I see. So you do need to define your own i18n files in the end if you wish to use any kind of translation...
I'd like to have more comments on this matter, please. Why not have lang files in GeoExt like OpenLayers do and use OpenLayers.i18n() directly in widgets instead of having to define them manually like your example below ? I agree that "text" is a big matter of "user customization" but having default values wouldn't hurt (I guess). Plus, translating a text could be done once and added to the project lang files instead of once per user using the widget. Thoughts ? Again, many thanks Bart. Alexandre [email protected] wrote: > Right, this is possible. > > For instance I construct such a widget with: > > this.printForm = new GeoExt.ux.SimplePrint({ > hideRotation: true, > defaults: {width: 200, listWidth: 200}, > layoutText: OpenLayers.i18n("mf.print.layout"), > dpiText: OpenLayers.i18n("mf.print.dpi"), > rotationText: OpenLayers.i18n("mf.print.rotation"), > scaleText: OpenLayers.i18n("mf.print.scale"), > printText: OpenLayers.i18n("mf.print.print"), > creatingPdfText: OpenLayers.i18n("mf.print.generatingPDF"), > ... > > and then I use my own language files. > > Best regards, > Bart > -- Alexandre Dubé Mapgears www.mapgears.com _______________________________________________ Dev mailing list [email protected] http://www.geoext.org/cgi-bin/mailman/listinfo/dev
