1164653 - Exposing Intl algorithms to Chrome code (or maybe even to teh Webs)

Status: RESOLVED WONTFIX

(Core :: JavaScript: Internationalization API, defect)

Description

[Marcos Caceres [:marcosc]]

The Intl.js built-in has some really useful functions for processing and dealing with language tags. It would be nice to expose those to chrome code somehow. 

For example, I'm having to process a language tag in something I'm implementing by doing:

Intl.Collator("foo").resolvedOptions().locale 

(Is there a better way?)

Comment 1

[Boris Zbarsky [:bzbarsky]]

The DOM doesn't have access to the Intl.js stuff directly.  That's all SpiderMonkey-internal.

Comment 2

[Jeff Walden [:Waldo]]

If these are useful to chrome code, they're probably useful to any code working with language tags.  That makes them a fair candidate for being in ECMAScript proper.  Could you send mail to https://mail.mozilla.org/listinfo/es-discuss pointing out the things you wish you could use, and how, so that they're considered for general exposure?  SpiderMonkey doesn't really implement things any more unless they're standards-track, basically.

Comment 3

[Gordon P. Hemsley [:GPHemsley]]

Isn't Intl already on the standards track? Isn't that what this whole Bugzilla component is about?

http://norbertlindenberg.com/2012/12/ecmascript-internationalization-api/index.html

Comment 4

[Gordon P. Hemsley [:GPHemsley]]

http://www.ecma-international.org/ecma-402/1.0/

Comment 5

[Jeff Walden [:Waldo]]

The Intl object is standardized, yes.  Comment 0 asks about particular algorithms in js/src/builtin/Intl.js that are specified for internal use in the ECMAScript Internationalization API, which includes the Intl object, but that are not *directly* exposed.

Comment 6

[Marcos Caceres [:marcosc]]

(In reply to Jeff Walden [:Waldo] (remove +bmo to email) from comment #5)
> The Intl object is standardized, yes.  Comment 0 asks about particular
> algorithms in js/src/builtin/Intl.js that are specified for internal use in
> the ECMAScript Internationalization API, which includes the Intl object, but
> that are not *directly* exposed.

Exactly, I want to access the algorithms for parsing language tags, etc. I can only access those indirectly right now.

Comment 7

[Marcos Caceres [:marcosc]]

(In reply to Jeff Walden [:Waldo] (remove +bmo to email) from comment #2)
> If these are useful to chrome code, they're probably useful to any code
> working with language tags.  That makes them a fair candidate for being in
> ECMAScript proper.  Could you send mail to
> https://mail.mozilla.org/listinfo/es-discuss pointing out the things you
> wish you could use, and how, so that they're considered for general
> exposure? 

Will do.

> SpiderMonkey doesn't really implement things any more unless
> they're standards-track, basically.
 
Makes sense. Closing.