Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Issue 28604 Expose some i18n apis via Javascript for dom UI and extensions
Starred by 19 users Project Member Reported by js...@chromium.org, Nov 23, 2009 Back to list
Status: Fixed
Owner: js...@chromium.org
Closed: Nov 2013
Cc: glen@chromium.org, oritm@chromium.org, eri...@gmail.com, erik.co...@gmail.com, arv@chromium.org, darin@chromium.org, ian@chromium.org, brettw@chromium.org
Components:
OS: All
Pri: 2
Type: Feature


Sign in to add a comment
This is a meta bug. 

Chrome comes with ICU (a rich i18n library for formatting and sorting to 
name just two examples) and the C++ part of Chrome can take full advantage 
of that. 

However, they are not available in Javascript. Therefore, neither dom UI 
nor extensions can use them.  

Traditional Javascript applications do the following:

* Include the locale-specific minimal data in the Javascript files and  use 
them for formatting (e.g. GWT-based Javascript apps do that). When a locale 
is changed, a new data has to be loaded, but that's pretty rare. 

  i18n'ized extensions can take this approach, too. Each locale directory 
will have locale-specific data, but if multiple extensions do that, there'd 
be multiple copies of data / JS libraries. 

* Talk to the server and ask them for sorted list. Obviously there's a 
latency issue. 

* Alternatively, send down the sort keys along with strings and binary-sort 
in terms of sort keys on the client side. This doesn't work well if what's 
to be sorted changes dynamically on the client-side. 

-----------------------------------

Moreover, in case of Chrome dom UI pages and extensions (and potentially 
"local apps" on Chrome OS), there's no "web server" to talk to. In the 
place of "web server", we have Chrome  with the full access to i18n apis. 
However, none of those APIs is exposed via Javascript. As a result, dom 
UI/extensions/local apps cannot use them.

For domUIs, we kinda worked around the issue by doing all the work in C++ 
and filling out html/js templates in C++. This works well for static data, 
but obviously doesn't work for dynamic data. 

One example is the # of recently closed tabs (plural formatting). See bug 
21407

The other is bug 28596 (perhaps, we can work around this issue, but leaving 
the current JS code alone would be nice). 

--------------------

We can expose some i18n apis in Javascript (V8 extensions?) in Chrome. Or, 
we can propose it to webkit or even higher up (like web apps WG). Sorting 
and date/time formatting are relatively easy to agree upon, but plural 
formatting would be tough to get consensus on (see bug 21407). 


 
Comment 1 by js...@chromium.org, Nov 23, 2009
Comment 2 by aa@chromium.org, Dec 12, 2009
Labels: mstone-x
Comment 3 by oritm@chromium.org, Dec 17, 2009
Labels: -Area-BrowserBackend Area-Internals
Labels Update:

Replace Area-BrowserBackend by Area-Internals
Comment 4 by oritm@chromium.org, Dec 18, 2009
Labels: -Area-BrowserUI Area-UI-Features
Area-UI-Features label replaces Area-BrowserUI label
Comment 5 by js...@chromium.org, Jan 21, 2010
http://wiki.opensocial.org/index.php?title=Gadgets.i18n_(v0.9) explains OpenSocial JS 
i18n library that takes the first approach in my bug report. 


Status: Assigned
Comment 7 by lafo...@chromium.org, Feb 17, 2010
Labels: -Area-UI-Features Area-UI
Comment 8 by js...@chromium.org, Feb 25, 2010
BTW, even a limited set of Javascript i18n apis are not well supported in Chrome at the 
moment. See bug 19254 and bug 3607 and the corresponding V8 bugs. 


Comment 10 by js...@chromium.org, Feb 26, 2010
Labels: Javascript
Comment 11 by js...@chromium.org, Feb 26, 2010
Comment 12 by js...@chromium.org, Mar 30, 2010
c.f. : http://cldrdata.appspot.com/  


Comment 13 by js...@chromium.org, Aug 12, 2010
http://wiki.ecmascript.org/doku.php?id=strawman:i18n_api

has the proposal we pitched to the ECMAScript WG (TC-39). 



Project Member Comment 14 by bugdroid1@chromium.org, Feb 10, 2011
The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=74491

------------------------------------------------------------------------
r74491 | cira@chromium.org | Thu Feb 10 14:06:07 PST 2011

Changed paths:
 M http://src.chromium.org/viewvc/chrome/trunk/src/build/features_override.gypi?r1=74491&r2=74490&pathrev=74491
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/renderer_host/browser_render_process_host.cc?r1=74491&r2=74490&pathrev=74491
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/renderer/render_thread.cc?r1=74491&r2=74490&pathrev=74491
 M http://src.chromium.org/viewvc/chrome/trunk/src/build/common.gypi?r1=74491&r2=74490&pathrev=74491
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/chrome_switches.cc?r1=74491&r2=74490&pathrev=74491
 M http://src.chromium.org/viewvc/chrome/trunk/src/webkit/tools/test_shell/test_shell_webkit_init.cc?r1=74491&r2=74490&pathrev=74491
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/chrome_switches.h?r1=74491&r2=74490&pathrev=74491

Adding support for JavaScript internationalization API as V8 extension. See proposal at http://wiki.ecmascript.org/doku.php?id=strawman:i18n_api.

V8 hosts the actual extension code under src/extensions/experimental/i18n-extension.{cc,h}.

This CL passes command line switches to WebKit (disabled by default) and test shell (enabled by default), using WebRuntimeFeatures. It also sets some gyp variables to point to ICU source path, and defines a guard for a new feature.

It should be submitted only after corresponding WebKit CL (https://bugs.webkit.org/show_bug.cgi?id=49414) lands.

BUG= 28604 
TEST=LayoutTests/fast/js/i18n-bindings-locale.html

Review URL: http://codereview.chromium.org/6366021
------------------------------------------------------------------------
Comment 15 by jat@google.com, Feb 17, 2011
I wish I had known about this proposal last year.  I think it is really great that JS would get some i18n APIs, but I think the proposal is insufficient.

As one example, getting the currency symbol from LocaleInfo seems useless - they are not guaranteed to be unique ("$"), so you can't use this to determine which currency the user is using, and it doesn't let you get the currency symbol for an arbitrary currency in the current locale.  So, for example, I don't see how GWT could make use of this for formatting numbers.

In general, the formatting functions are underspecified -- exactly what do they do, and what are valid options that might be passed in?

For number formatting, are you expected to pass a format pattern as options?  It is rarely sufficient to just use one default format, but you do want decimal and thousands separators substituted appropriately.

For dates, how do I select a particular date format?  Can I choose a locale-appropriate format given a skeleton pattern?

Overall, I am happy to see some progress in this area, but I think it would be better to expose functionality closer to ICU and exposing more of the information available from CLDR.
Comment 16 by js...@chromium.org, Mar 3, 2011
Our original proposal has been a lot more comprehensive than the current draft, but we had to scale down significantly to inlcude only what's easily and quickly implementable by multiple parties. 

As for the currency, the currency coming out of LocaleInfo is 'the most likely' one, but needless to say, that does not mean that it's the one actually used in a particular transaction. (en-US speaker can buy a thing in JPY from a Japanese online store, for instance). 

Project Member Comment 17 by bugdroid1@chromium.org, Mar 10, 2011
Comment 18 by lafo...@chromium.org, Mar 18, 2011
Labels: -I18N bulkmove Feature-I18N
This is a meta bug. 

Chrome comes with ICU (a rich i18n library for formatting and sorting to 
name just two examples) and the C++ part of Chrome can take full advantage 
of that. 

However, they are not available in Javascript. Therefore, neither dom UI 
nor extensions can use them.  

Traditional Javascript applications do the following:

* Include the locale-specific minimal data in the Javascript files and  use 
them for formatting (e.g. GWT-based Javascript apps do that). When a locale 
is changed, a new data has to be loaded, but that's pretty rare. 

  i18n'ized extensions can take this approach, too. Each locale directory 
will have locale-specific data, but if multiple extensions do that, there'd 
be multiple copies of data / JS libraries. 

* Talk to the server and ask them for sorted list. Obviously there's a 
latency issue. 

* Alternatively, send down the sort keys along with strings and binary-sort 
in terms of sort keys on the client side. This doesn't work well if what's 
to be sorted changes dynamically on the client-side. 

-----------------------------------

Moreover, in case of Chrome dom UI pages and extensions (and potentially 
"local apps" on Chrome OS), there's no "web server" to talk to. In the 
place of "web server", we have Chrome  with the full access to i18n apis. 
However, none of those APIs is exposed via Javascript. As a result, dom 
UI/extensions/local apps cannot use them.

For domUIs, we kinda worked around the issue by doing all the work in C++ 
and filling out html/js templates in C++. This works well for static data, 
but obviously doesn't work for dynamic data. 

One example is the # of recently closed tabs (plural formatting). See bug 
21407

The other is bug 28596 (perhaps, we can work around this issue, but leaving 
the current JS code alone would be nice). 

--------------------

We can expose some i18n apis in Javascript (V8 extensions?) in Chrome. Or, 
we can propose it to webkit or even higher up (like web apps WG). Sorting 
and date/time formatting are relatively easy to agree upon, but plural 
formatting would be tough to get consensus on (see bug 21407).
Comment 19 by js...@chromium.org, Apr 18, 2011
Collator was added to V8 bleeding edge last week and it's now in V8 trunk. Chrome trunk will get it very soon. 

http://code.google.com/p/v8/source/detail?spec=svn7649&r=7620 

Add v8Locale.Collator

This is a partial implementation of Collator per what's agreed upon at the last
ECMAScript meeting + mailing list. Only the following three options are
implemented: ignoreAccent, ignoreCase, numeric.

ChromeOS and Chrome need this feature for M12. This could be added as chrome
extension API. Giiven that we have a rough agreement on the collation part of
ECMAScript API, we thought it'd save us some duplicated work adding this to v8
(experimental i18n api) now rather than implementing it in Chrome now and moving
it later.


BUG= 28604 
TEST=http://i18nl10n.com/chrome/coll2.html
Review URL: http://codereview.chromium.org/6673011


Comment 20 by js...@chromium.org, Apr 20, 2011
v8Locale.Collator is now in the Chrome trunk and will be in for R12 branch.

Comment 21 by rahulrc@chromium.org, May 13, 2011
Labels: -mstone-x
Comment 22 by js...@chromium.org, May 25, 2011
It turned out that Collation didn't make it M12 branch. The code was checked into v8 bleeding edge a few days before the cut-off and in turn, it's promoted to v8 tag 3.x.y.z, which was pulled into Chrome trunk before the branch cut-off. However, DEPS file we actually use for the M12 build has a v8 version earlier than that. 


Cc: -ian.chro...@gmail.com ian@chromium.org
Project Member Comment 24 by bugdroid1@chromium.org, Jul 25, 2011
Cc: eri...@gmail.com
The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=93861

------------------------------------------------------------------------
r93861 | jshin@chromium.org | Mon Jul 25 02:19:35 PDT 2011

Changed paths:
 A http://src.chromium.org/viewvc/chrome/trunk/deps/third_party/icu46/cros/data/curr/reslocal.mk?r1=93861&r2=93860&pathrev=93861
 M http://src.chromium.org/viewvc/chrome/trunk/deps/third_party/icu46/patches/locale3.patch?r1=93861&r2=93860&pathrev=93861
 M http://src.chromium.org/viewvc/chrome/trunk/deps/third_party/icu46/source/data/curr/reslocal.mk?r1=93861&r2=93860&pathrev=93861
 A http://src.chromium.org/viewvc/chrome/trunk/deps/third_party/icu46/cros/data/curr?r1=93861&r2=93860&pathrev=93861

Add the currency display name for JavaScript I18N API

This CL does not update the pre-built ICU data files. They'll be
added in the next CL.

It'll increase the ICU data file about 900kB (uncompressed). 

BUG= 28604 
TEST=No test yet until pre-built data files are checked in and rolled in via DEPS file update.
TBR=cira
Review URL: http://codereview.chromium.org/7488050
------------------------------------------------------------------------
Labels: Hotlist-GoogleApps
Project Member Comment 26 by bugdroid1@chromium.org, May 3, 2012
The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=135101

------------------------------------------------------------------------
r135101 | cira@chromium.org | Wed May 02 22:35:11 PDT 2012

Changed paths:
 M http://src.chromium.org/viewvc/chrome/trunk/src/DEPS?r1=135101&r2=135100&pathrev=135101

Roll v8-i18n to r64.

This change adds new v8Intl global namespace and new API that reflects the current EcmaScript 402 draft - http://wiki.ecmascript.org/doku.php?id=globalization:specification_drafts.

The old v8Locale is still available, so the current users won't notice this addition.

BUG= 28604 
TEST=

Review URL: http://codereview.chromium.org/10321004
------------------------------------------------------------------------
Project Member Comment 27 by bugdroid1@chromium.org, May 3, 2012
The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=135106

------------------------------------------------------------------------
r135106 | jochen@chromium.org | Thu May 03 01:58:29 PDT 2012

Changed paths:
 M http://src.chromium.org/viewvc/chrome/trunk/src/DEPS?r1=135106&r2=135105&pathrev=135106

Revert 135101 - Roll v8-i18n to r64.

This change adds new v8Intl global namespace and new API that reflects the current EcmaScript 402 draft - http://wiki.ecmascript.org/doku.php?id=globalization:specification_drafts.

The old v8Locale is still available, so the current users won't notice this addition.

BUG= 28604 
TEST=

Review URL: http://codereview.chromium.org/10321004

TBR=cira@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10348008
------------------------------------------------------------------------
Comment 28 by arv@chromium.org, May 3, 2012
Any chance you can add a console.warn if they access v8locale?
Project Member Comment 29 by bugdroid1@chromium.org, May 9, 2012
The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=135972

------------------------------------------------------------------------
r135972 | cira@chromium.org | Tue May 08 19:20:35 PDT 2012

Changed paths:
 M http://src.chromium.org/viewvc/chrome/trunk/src/DEPS?r1=135972&r2=135971&pathrev=135972

Roll v8-i18n to r66.

This change adds new v8Intl global namespace and new API that reflects the current EcmaScript 402 draft - http://wiki.ecmascript.org/doku.php?id=globalization:specification_drafts.

The old v8Locale is still available, so the current users won't notice the addition.

License header in collator.h was updated.

Some collator extension keys were removed per spec.

Code was restructured so it doesn't add three new static initializations to CHrome startup.

Memory leaks fixed.

BUG= 28604 
TEST=
NOTRY=true

Review URL: https://chromiumcodereview.appspot.com/10381038
------------------------------------------------------------------------
Project Member Comment 30 by bugdroid1@chromium.org, May 9, 2012
The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=135976

------------------------------------------------------------------------
r135976 | cira@chromium.org | Tue May 08 19:46:05 PDT 2012

Changed paths:
 M http://src.chromium.org/viewvc/chrome/trunk/src/DEPS?r1=135976&r2=135975&pathrev=135976

Revert 135972 - Roll v8-i18n to r66.

The change breaks Linux builder wrt. sizes. Reverting till tomorrow.

This change adds new v8Intl global namespace and new API that reflects the current EcmaScript 402 draft - http://wiki.ecmascript.org/doku.php?id=globalization:specification_drafts.

The old v8Locale is still available, so the current users won't notice the addition.

License header in collator.h was updated.

Some collator extension keys were removed per spec.

Code was restructured so it doesn't add three new static initializations to CHrome startup.

Memory leaks fixed.

BUG= 28604 
TEST=
NOTRY=true

Review URL: https://chromiumcodereview.appspot.com/10381038

TBR=cira@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10378064
------------------------------------------------------------------------
Project Member Comment 31 by bugdroid1@chromium.org, May 10, 2012
The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=136252

------------------------------------------------------------------------
r136252 | cira@chromium.org | Thu May 10 00:03:26 PDT 2012

Changed paths:
 M http://src.chromium.org/viewvc/chrome/trunk/src/DEPS?r1=136252&r2=136251&pathrev=136252

Roll v8-i18n 32:67.

This change adds new v8Intl global namespace and new API that reflects the current EcmaScript 402 draft - http://wiki.ecmascript.org/doku.php?id=globalization:specification_drafts.

The old v8Locale is still available, so the current users won't notice the addition.

BUG= 28604 
TEST=


Review URL: https://chromiumcodereview.appspot.com/10383097
------------------------------------------------------------------------
Project Member Comment 32 by bugdroid1@chromium.org, May 17, 2012
Blocking: -21407 -28596 -71475 chromium:21407 chromium:28596 chromium:71475
The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=137772

------------------------------------------------------------------------
r137772 | cira@chromium.org | Thu May 17 16:44:10 PDT 2012

Changed paths:
 M http://src.chromium.org/viewvc/chrome/trunk/src/DEPS?r1=137772&r2=137771&pathrev=137772

Roll v8-i18n 67:89.

- Added testing infrastructure + tests.
- Spec changes reflected in code.
- Documentation updates.

TBR=jshin@chromium.org
BUG= 28604 
TEST=See http://code.google.com/p/v8-i18n/wiki/Testing.


Review URL: https://chromiumcodereview.appspot.com/10386196
------------------------------------------------------------------------
Project Member Comment 33 by bugdroid1@chromium.org, May 18, 2012
The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=137781

------------------------------------------------------------------------
r137781 | fischman@chromium.org | Thu May 17 17:24:53 PDT 2012

Changed paths:
 M http://src.chromium.org/viewvc/chrome/trunk/src/DEPS?r1=137781&r2=137780&pathrev=137781

Revert 137772 - Roll v8-i18n 67:89.

- Added testing infrastructure + tests.
- Spec changes reflected in code.
- Documentation updates.

TBR=jshin@chromium.org
BUG= 28604 
TEST=See http://code.google.com/p/v8-i18n/wiki/Testing.


Review URL: https://chromiumcodereview.appspot.com/10386196

TBR=cira@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10332232
------------------------------------------------------------------------
Project Member Comment 34 by bugdroid1@chromium.org, May 18, 2012
The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=137938

------------------------------------------------------------------------
r137938 | cira@chromium.org | Fri May 18 13:12:58 PDT 2012

Changed paths:
 M http://src.chromium.org/viewvc/chrome/trunk/src/DEPS?r1=137938&r2=137937&pathrev=137938

Roll v8-i18n 67:90.

- Added testing infrastructure + tests.
- Spec changes reflected in code.
- Documentation updates.
- License fix

TBR=jshin@chromium.org
BUG= 28604 
TEST=See http://code.google.com/p/v8-i18n/wiki/Testing.


Review URL: https://chromiumcodereview.appspot.com/10389207
------------------------------------------------------------------------
Project Member Comment 35 by bugdroid1@chromium.org, May 24, 2012
The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=138835

------------------------------------------------------------------------
r138835 | cira@chromium.org | Thu May 24 11:07:12 PDT 2012

Changed paths:
 M http://src.chromium.org/viewvc/chrome/trunk/src/DEPS?r1=138835&r2=138834&pathrev=138835

Roll v8-i18n 90:104

- Spec change reflected in code
- More documentation and tests

TBR=jshin@chromium.org
BUG= 28604 
TEST=See http://code.google.com/p/v8-i18n/wiki/Testing


Review URL: https://chromiumcodereview.appspot.com/10423009
------------------------------------------------------------------------
Comment 36 by js...@chromium.org, Jul 30, 2012
Blocking: chromium:3607
Project Member Comment 37 by bugdroid1@chromium.org, Aug 9, 2012
The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=150842

------------------------------------------------------------------------
r150842 | cira@chromium.org | 2012-08-09T17:53:23.242018Z

Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/DEPS?r1=150842&r2=150841&pathrev=150842

v8-i18n roll 105:117.

Removes support for v8Locale. ChromeOS has already moved to new v8Intl.

BUG= 28604 
TEST=v8Locale should not exist. ChromeOS should build properly.


Review URL: https://chromiumcodereview.appspot.com/10837152
------------------------------------------------------------------------
Project Member Comment 38 by bugdroid1@chromium.org, Aug 13, 2012
Labels: merge-merged-1229
The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=151295

------------------------------------------------------------------------
r151295 | cira@chromium.org | 2012-08-13T17:21:14.153623Z

Changed paths:
   M http://src.chromium.org/viewvc/chrome/branches/1229/src/DEPS?r1=151295&r2=151294&pathrev=151295

Merge 150842 - v8-i18n roll 105:117.

Removes support for v8Locale. ChromeOS has already moved to new v8Intl.

BUG= 28604 
TEST=v8Locale should not exist. ChromeOS should build properly.


Review URL: https://chromiumcodereview.appspot.com/10837152

TBR=inferno@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10834293
------------------------------------------------------------------------
Project Member Comment 39 by bugdroid1@chromium.org, Oct 2, 2012
Blocking: -chromium:21407 -chromium:28596 -chromium:71475 chromium:21407 chromium:28596 chromium:71475
The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=159741

------------------------------------------------------------------------
r159741 | cira@chromium.org | 2012-10-02T19:32:17.352044Z

Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/DEPS?r1=159741&r2=159740&pathrev=159741

Roll v8-i18n 143:150.

This change introduces Intl global object.
The original v8Intl is aliased to Intl to prevent client problems (ChromeOS, Drive, some Chrome apps).

The Intl name is part of new ECMA 402 standard.

See https://codereview.appspot.com/6598047/ for details.

TEST=Open console in Chrome. Both Intl and v8Intl should be there. v8Intl === Intl.

BUG= 28604 


Review URL: https://chromiumcodereview.appspot.com/11040008
------------------------------------------------------------------------
Project Member Comment 40 by bugdroid1@chromium.org, Oct 17, 2012
The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=162444

------------------------------------------------------------------------
r162444 | cira@chromium.org | 2012-10-17T17:41:31.092926Z

Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/DEPS?r1=162444&r2=162443&pathrev=162444

Roll v8-i18n 151:153.

Removal of normalization support for collator (on by default).
See https://codereview.appspot.com/6693045/ for details.

BUG= 28604 
TEST=Test added to the v8-i18n library that checks proper behavior.


Review URL: https://chromiumcodereview.appspot.com/11203002
------------------------------------------------------------------------
Project Member Comment 41 by bugdroid1@chromium.org, Oct 27, 2012
The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=164513

------------------------------------------------------------------------
r164513 | cira@chromium.org | 2012-10-27T06:02:51.310270Z

Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/DEPS?r1=164513&r2=164512&pathrev=164513

Roll v8-i18n, 153:155.

Support for IANA time zones in date formatting.

TBR=jshin@chromium.org
TEST=Added tests/intl/date-format/timezone.js test to v8-i18.
BUG= 28604 


Review URL: https://chromiumcodereview.appspot.com/11304016
------------------------------------------------------------------------
Project Member Comment 42 by bugdroid1@chromium.org, Mar 10, 2013
Labels: -Feature-Extensions -Area-Internals -Area-UI -Feature-I18N Cr-Platform-Extensions Cr-UI Cr-Internals Cr-UI-I18N
Project Member Comment 43 by bugdroid1@chromium.org, Mar 20, 2013
Labels: -Cr-UI-I18N Cr-UI-Internationalization
Comment 44 by js...@chromium.org, Nov 25, 2013
Status: Fixed
Let's close this down. EcmaScript now has I18N API defined and we implemented all the version 1 features. Initially, it's a v8 extension, but now is a part of v8 proper. 

Other features (v2) are being spec'd out and can be tracked separately. 

Sign in to add a comment