On Tue, Aug 30, 2011 at 12:49 AM, mortac8 <[email protected]> wrote: > I have code that does: > OpenLayers.Lang.en.baseLayer="Base Map"; > > If I include the built version of OpenLayers 2.11rc3 and launch my > application, I get a "OpenLayers.Lang.en is undefined" error. This did not > happen in 2.10. > > Is there a way around this? It works if I include /lib/OpenLayers.js > instead of the built /OpenLayers.js. > > Any thought are appreciated.
SingleFile.js does indeed not include a "@requires OpenLayers/Lang/en.js" statement, so builds created with full.cfg don't include en.js. Things are indeed different in 2.10. In 2.10 both SingleFile.js and OpenLayers.js are included in builds, and the latter does @require en.js. I think it's a good thing that 2.11 allows creating builds that don't include en.js. People wanting en.js (or other language files) in their OpenLayers builds need to add "OpenLayers/Lang/en.js" in the [include] section of their build configuration files. Ashley, you can try that and see if it works for you. Now we can wonder whether OpenLayers builds provided at http://openlayers.org/api should include en.js or not. With changeset 12127 [*] by Tim I think we don't need to have en.js in our OpenLayers.js builds. [*] <http://trac.osgeo.org/openlayers/changeset/12127> -- Eric Lemoine Camptocamp France SAS Savoie Technolac, BP 352 73377 Le Bourget du Lac, Cedex Tel : 00 33 4 79 44 44 96 Mail : [email protected] http://www.camptocamp.com _______________________________________________ Users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/openlayers-users
