> We now have access to vendored-in ICU and expose Intl.NumberFormat in JS. I'm going to attempt to translate this sentence into English: ------ We now imported a third party library for the "International Components for Unicode" (see https://phrase.com/blog/posts/guide-to-the-icu-message-format/ ), which allows us to find the correct number format for the current locale. We are exposing that to JavaScript code using a new API Intl/NumberFormat (see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/NumberFormat ). That means that any JavaScript code can now consider the locale's number format. However, all code that wants to use the correct number format must be changed to use the new API. ------ Did I translate this correctly? Also, doesn't that mean that this bug is now either FIXED (because the request here was implemented in the code) or a DUPLICATE of the bug where the implementation happened?
Bug 74716 Comment 15 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
> We now have access to vendored-in ICU and expose Intl.NumberFormat in JS. I'm going to attempt to translate this sentence into English that other software developers can understand: ------ We now imported a third party library for the "International Components for Unicode" (see https://phrase.com/blog/posts/guide-to-the-icu-message-format/ ), which allows us to find the correct number format for the current locale. We are exposing that to JavaScript code using a new API Intl/NumberFormat (see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/NumberFormat ). That means that any JavaScript code can now consider the locale's number format. However, all code that wants to use the correct number format must be changed to use the new API. ------ Did I translate this correctly? Also, doesn't that mean that this bug is now either FIXED (because the request here was implemented in the code) or a DUPLICATE of the bug where the implementation happened?
> We now have access to vendored-in ICU and expose Intl.NumberFormat in JS. I'm going to attempt to translate this sentence into English that other software developers can understand: ------ We now imported a third party library for the "International Components for Unicode" (see https://phrase.com/blog/posts/guide-to-the-icu-message-format/ ), which allows us to find the correct number format for the current locale. We are exposing that to JavaScript code using a new API `Intl.NumberFormat` (see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/NumberFormat ). That means that any JavaScript code can now consider the locale's number format. However, all code that wants to use the correct number format must be changed to use the new API. ------ Did I translate this correctly? Also, doesn't that mean that this bug is now either FIXED (because the request here was implemented in the code) or a DUPLICATE of the bug where the implementation happened?
> We now have access to vendored-in ICU and expose Intl.NumberFormat in JS. I'm going to attempt to translate this sentence into English for other software developers: ------ We now imported a third party library for the "International Components for Unicode" (see https://phrase.com/blog/posts/guide-to-the-icu-message-format/ ), which allows us to find the correct number format for the current locale. We are exposing that to JavaScript code using a new API `Intl.NumberFormat` (see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/NumberFormat ). That means that any JavaScript code can now consider the locale's number format. However, all code that wants to use the correct number format must be changed to use the new API. ------ Did I translate this correctly? Also, doesn't that mean that this bug is now either FIXED (because the request here was implemented in the code) or a DUPLICATE of the bug where the implementation happened?
> We now have access to vendored-in ICU and expose Intl.NumberFormat in JS. I'm going to attempt to translate this sentence into English for normal software developers: ------ We now imported a third party library for the "International Components for Unicode" (see https://phrase.com/blog/posts/guide-to-the-icu-message-format/ ), which allows us to find the correct number format for the current locale. We are exposing that to JavaScript code using a new API `Intl.NumberFormat` (see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/NumberFormat ). That means that any JavaScript code can now consider the locale's number format. However, all code that wants to use the correct number format must be changed to use the new API. ------ Did I translate this correctly? Also, doesn't that mean that this bug is now either FIXED (because the request here was implemented in the code) or a DUPLICATE of the bug where the implementation happened?
> We now have access to vendored-in ICU and expose Intl.NumberFormat in JS. I'm going to attempt to translate this sentence into English for other software developers: ------ We now imported a third party library for the "International Components for Unicode" (see https://phrase.com/blog/posts/guide-to-the-icu-message-format/ ), which allows us to find the correct number format for the current locale. We are exposing that to JavaScript code using a new API `Intl.NumberFormat` (see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/NumberFormat ). That means that any JavaScript code can now consider the locale's number format. However, all code that wants to use the correct number format must be changed to use the new API. ------ Did I translate this correctly? Also, doesn't that mean that this bug is now either FIXED (because the request here was implemented in the code) or a DUPLICATE of the bug where the implementation happened?
> We now have access to vendored-in ICU and expose Intl.NumberFormat in JS. I'm going to attempt to translate this sentence into English, for other software developers: ------ We now imported a third party library for the "International Components for Unicode" (see https://phrase.com/blog/posts/guide-to-the-icu-message-format/ ), which allows us to find the correct number format for the current locale. We are exposing that to JavaScript code using a new API `Intl.NumberFormat` (see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/NumberFormat ). That means that any JavaScript code can now consider the locale's number format. However, all code that wants to use the correct number format must be changed to use the new API. ------ Did I translate this correctly? Also, doesn't that mean that this bug is now either FIXED (because the request here was implemented in the code) or a DUPLICATE of the bug where the implementation happened?