Localized Graphs and Tables

@dsjen @rocha
I believe we can do something like:

```
define([
    'globalize',
    'vendor/json!vendor/cldr/supplemental/likelySubtags.json',
    'globalize/number'],
    function (Globalize, likelySubtags, _number) {
        'use strict';

        var languageCode;

        Globalize.fixLanguageCode = function (code) {
            if (!code || typeof code !== 'string') {
                return 'en';
            }

            code = code.toLowerCase();

            // Django uses zh-cn. CLDR uses zh.
            if (languageCode === 'zh-cn') {
                return 'zh';
            }

            // There doesn't seem to be an onFailure event for the text! plugin. Make sure we only pass valid language codes
            // so the plugin does not attempt to load non-existent files.
            if (['ar', 'ca', 'cs', 'da', 'de', 'el', 'en-001', 'en-au', 'en-ca', 'en-gb', 'en-hk', 'en-in', 'en', 'es', 'fi',
                'fr', 'he', 'hi', 'hr', 'hu', 'it', 'ja', 'ko', 'nb', 'nl', 'pl', 'pt-pt', 'pt', 'ro', 'root', 'ru', 'sk', 'sl',
                'sr', 'sv', 'th', 'tr', 'uk', 'vi', 'zh-hant', 'zh'].indexOf(languageCode) > -1) {
                return code;
            }
            return 'en';
        };

        languageCode = Globalize.fixLanguageCode(window.language);

        // initialize tracking
        require(['vendor/json!vendor/cldr/main/' + languageCode + '/numbers.json'],
            function(numbers){
                Globalize.load(numbers);
            }
        );

        Globalize.load(likelySubtags);

        return Globalize(languageCode);
});
```

We won't pollute the global namespace by encapsulating this in a module.