Cornelius, Thanks for your very well detailed answer. I'll go with the simplePrint method that Bart suggested (resulting in a file with a bunch text overwritten named fr.js for example).
Devs, would it make sense to at least keep these translation files inside GeoExt resource/lang/ directory ? Users might find it handy to have already translated widgets IMHO. Alexandre Cornelius Weiss wrote: > Please note, that the approach like with simplePrint is already > lang-file capable > > //example: > File with statments like this: > GeoExt.ux.SimplePrint.prototype.layoutText = 'translated text...'; -- Alexandre Dubé Mapgears www.mapgears.com _______________________________________________ Dev mailing list [email protected] http://www.geoext.org/cgi-bin/mailman/listinfo/dev
