Hi,
My site (http://lipik.in) does not work with dojo 1.5. The issue is that new parser propagates the lang attribute to contained widgets in the page, whereas I was using it purely as a selector for fonts. It would be OK if dojo could guarantee sensible default with arbitrary lang, instead of falling over with the error "Bundle not found: loading in dijit , locale=hi". It seems to me that dijit widgets can no longer be used on a page that specifies the lang to a value whose corresponding NLS bundle is not available in the custom build.
I looked at the parser code: there is no way to revert the parsing to old behaviour (i.e. please ignore lang & dir) - i.e. this is a regression. But on a practical note, is there a way to fall back to the locale specified in djConfig.locale if the bundle corresponding to widget.lang can't be loaded? Note the 2nd option is still sub-optimal, since it would involve failed requests to the server.
I know this is not typical usage etc, but I think the bottom line with lang attribute is that it is never prescriptive - i.e. there is no value of lang for which the page will be ill-formed. But with the dojo NLS loading algorithm, some lang values are being treated as 'invalid', leading to page not loading.
For completeness, my app specifies djConfig.locale="en-us" and the build command-line has the parameter localeList=en-us with extraLocale not specified.
Thanks