$locale service should also provide directionality information

[gilshwartz]

Current i18n ground work provides number, date, currency, and plural information. Since some of the languages are written rtl (right to left) and not ltr (left to right), I believe this information (language directionality) needs to be added to the $locale service for each language/locale.

[GBR-613]

Dear AngularJS team,

(Despite this is old issue I am happy that it exists, otherwise I would need to open it by myself :))

According to your CONTRIBUTING.md you import all your i18n information from the Google Closure I18N library. The information regarding language directionality is available in Closure, however currently it is not imported among other i18n. Presence of this information is important for several projects on which my team works, and I would like necessary solution and to offer it to let others enjoy it as well (except if you would prefer to do that by yourselves).

The necessary functionality is available in closure/goog/i18n/bidi.js file, function goog.i18n.bidi.isRtlLanguage(). As far as I understand I will need to change script update-closure.sh to import the necessary code and closureSlurper.js to proceed with it, is that correct?

Before I start to work on the code, appreciate if you could tell me if the change can be acceptable for you in principle.

Thanks in advance!

[tomerm]

The original information about natural direction of script can be found in CLDR. Specifically, correlation between language and natural direction traced via language (locale) .--> script --> direction.
Correlation between language and script is defined here: http://www.unicode.org/cldr/charts/latest/supplemental/languages_and_scripts.html
Direction of script is defined here: http://unicode.org/cldr/trac/browser/trunk/common/properties/scriptMetadata.txt