Thank you for your thoughts, all. I filed an issue with HTML - https://github.com/whatwg/html/issues/4630
☆*PhistucK* On Wed, May 15, 2019 at 10:52 PM Shane Carr <s...@google.com> wrote: > Hi PhistucK, > > Thanks for the feedback! Adding HTML for Intl features would be out of > scope for this feature. We already have JavaScript-based i18n features > like Intl.NumberFormat, Intl.DateFormat, etc., and Intl.DisplayNames is > being implemented in the same fashion. > > You may be interested in discussions such as: > > https://github.com/tc39/ecma402/issues/92 > > You can also open a new thread on the ECMA 402 repo. > > Shane > > On Wed, May 15, 2019 at 9:48 AM Frank Tang <ft...@chromium.org> wrote: > >> Sorry, I am not quite sure what you mean. It seems to me a suggestion of >> proposing additional standard in HTML spec. Do you mind to raise the issue >> in https://github.com/tc39/proposal-intl-displaynames/issues with more >> information so other members in ECMA402 subcommittee can help me to take >> action to talk to the related parties? >> >> Thanks >> >> On Mon, May 13, 2019 at 10:41 PM PhistucK <phist...@gmail.com> wrote: >> >>> I wonder whether this should be accompanied by an HTML equivalent >>> declarative way of displaying those strings, otherwise the HTML strings >>> might be left blank or JavaScript will be required for filling up what >>> could sometimes be simple forms that were simply internationalized. >>> Pseudo-code example - >>> <label> >>> <intl template="state-or-province">State/province</intl>: >>> <input type="text" required="required" name="state-or-province"/> >>> </label> >>> >>> >>> ☆*PhistucK* >>> >>> >>> On Tue, May 14, 2019 at 5:03 AM Frank Tang <ft...@chromium.org> wrote: >>> >>>> >>>> >>>> On Mon, May 13, 2019 at 6:56 PM 'Frank Tang (譚永鋒)' via v8-dev < >>>> v8-dev@googlegroups.com> wrote: >>>> >>>>> >>>>> >>>>> *From: *Mathias Bynens <m...@google.com> >>>>> *Date: *Mon, 13 May 2019 at 18:08 >>>>> *To: *Frank Tang >>>>> *Cc: *v8-users, blink-dev, Adam Klein, Frank Yung-Fong Tang, Sathya >>>>> Gunasekaran, Nebojša Ćirić, <v8-dev@googlegroups.com>, Jungshik Shin, >>>>> Shane Carr >>>>> >>>>> Can the doc at https://goo.gl/im9wy4 be made public please? >>>>>> >>>>> >>>>> It always is. >>>>> >>>> >>>> sorry it was not. I got confused since I shared with my other account. >>>> It is now. >>>> >>>>> >>>>> >>>>>> >>>>>> Usually we only implement features at stage 3. What’s the motivation >>>>>> for implementing this particular API earlier? (Not saying I’m opposed to >>>>>> it.) >>>>>> >>>>> >>>>> Since I am the champion of the proposal itself, having a prototype >>>>> implementation help me to figure out some tricky issues in the >>>>> specification level. In specific, tricky issues about speed, memory and >>>>> size that might be avoid if I specify differently. Sometime these thing >>>>> won't be obvious until implementation. Of course, we can wait till stage 3 >>>>> then implement it, and then if we find out tricky issues which will >>>>> increase binary size or cause latency problem, we will have to go back to >>>>> request to change the specification. >>>>> >>>>> >>>>> >>>>>> *From: *Frank Tang <ft...@chromium.org> >>>>>> *Date: *Mon, May 13, 2019 at 9:43 PM >>>>>> *To: *v8-users, blink-dev, Adam Klein, Frank Yung-Fong Tang, Sathya >>>>>> Gunasekaran, Mathias Bynens, Nebojša Ćirić, <v8-dev@googlegroups.com>, >>>>>> Jungshik Shin, Shane Carr >>>>>> >>>>>> Title: Intent to Implement: Intl.DisplayNames API Proposal >>>>>>> >>>>>>> >>>>>>> >>>>>>> Contact emails >>>>>>> >>>>>>> ft...@chromium.com >>>>>>> >>>>>>> >>>>>>> >>>>>>> Explainer >>>>>>> >>>>>>> https://github.com/tc39/proposal-intl-displaynames >>>>>>> >>>>>>> https://tc39.github.io/proposal-intl-displaynames/ >>>>>>> >>>>>>> >>>>>>> Design doc/Spec >>>>>>> >>>>>>> Engineering Plan https://goo.gl/im9wy4 >>>>>>> >>>>>>> >>>>>>> Summary >>>>>>> >>>>>>> Provides a new API to get localized names of language, region, >>>>>>> script, currency codes of international standard as well as commonly >>>>>>> used >>>>>>> names of date fields and symbols. >>>>>>> >>>>>>> >>>>>>> Motivation >>>>>>> >>>>>>> Main motivation for Intl.DisplayNames project was to enable >>>>>>> developers to get translation of language, region or script display >>>>>>> names >>>>>>> on the client. Translation of languages, regions or script display names >>>>>>> requires large amount of data to transmit on the network, which is >>>>>>> already >>>>>>> available in most browsers. These display name translations also carry >>>>>>> steep data size penalty for developers. This API will allow web >>>>>>> developers >>>>>>> to shrink the size of their HTML and/ or ECMAScript code without the >>>>>>> need >>>>>>> to include the human readable form of display names and therefore reduce >>>>>>> the download size to decrease latency. Also, this API will reduce the >>>>>>> localization cost for the web developers. Our goal is to expose this >>>>>>> data >>>>>>> through Intl API for use in e.g. language, region and script pickers, >>>>>>> etc. >>>>>>> >>>>>>> >>>>>>> Benefit >>>>>>> >>>>>>> - >>>>>>> >>>>>>> Reduce download size of apps and therefore improve latency. >>>>>>> - >>>>>>> >>>>>>> Easy for users to build internationalized language, region or >>>>>>> script selection UI components (drop down menu or other kinds). >>>>>>> - >>>>>>> >>>>>>> Reduce translation cost for developers. >>>>>>> - >>>>>>> >>>>>>> Consistent translation of language, region and script display >>>>>>> name on the web. >>>>>>> >>>>>>> >>>>>>> Risks >>>>>>> >>>>>>> Interoperability and Compatibility >>>>>>> >>>>>>> This is a new API. It is currently under TC39 Stage 1 and we plan to >>>>>>> propose to advance it to Stage 2 in June 2019. >>>>>>> >>>>>>> >>>>>>> Ergonomics >>>>>>> >>>>>>> >>>>>>> Activation >>>>>>> >>>>>>> Web developers could use the API immediately upon our shipment. >>>>>>> >>>>>>> >>>>>>> Debuggability >>>>>>> >>>>>>> Nothing special. >>>>>>> >>>>>>> >>>>>>> >>>>>>> Will this feature be supported on all six Blink platforms (Windows, >>>>>>> Mac, Linux, Chrome OS, Android, and Android WebView)? >>>>>>> >>>>>>> Yes. >>>>>>> >>>>>>> >>>>>>> Is this feature fully tested by web-platform-tests >>>>>>> <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md> >>>>>>> ? >>>>>>> >>>>>>> Tests under tc39/test262 will includes many tests to test this API. >>>>>>> >>>>>>> >>>>>>> Link to entry on the feature dashboard >>>>>>> <https://www.chromestatus.com/> >>>>>>> >>>>>>> https://www.chromestatus.com/feature/4965112605573120 >>>>>>> >>>>>>> >>>>>>> Requesting approval to ship? >>>>>>> >>>>>>> “No”. The feature is behind a runtime flag >>>>>>> harmony_intl_display_names and I will later send an Intent to Ship >>>>>>> <https://docs.google.com/a/chromium.org/document/d/1EyRTYnF2bmgqwYQQTDs2R2BT3ZSx29iPCFKTQiS_37o/edit> >>>>>>> email when I am ready to enable by default. >>>>>>> >>>>>> >>>>> >>>>> -- >>>>> Frank Yung-Fong Tang >>>>> 譚永鋒 / 🌭🍊 >>>>> Sr. Software Engineer >>>>> >>>>> -- >>>>> -- >>>>> v8-dev mailing list >>>>> v8-dev@googlegroups.com >>>>> http://groups.google.com/group/v8-dev >>>>> --- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "v8-dev" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to v8-dev+unsubscr...@googlegroups.com. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/v8-dev/CA%2B7fzPEZnnAGHh6mijLRByRm2A1xrgNFjSLr3gWf5Qs42bShrA%40mail.gmail.com >>>>> <https://groups.google.com/d/msgid/v8-dev/CA%2B7fzPEZnnAGHh6mijLRByRm2A1xrgNFjSLr3gWf5Qs42bShrA%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "blink-dev" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to blink-dev+unsubscr...@chromium.org. >>>> To view this discussion on the web visit >>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOcELL8wEy1NrdM10dd9xPmBmrUuy8CrV95eHoOwdg_TzhmLnw%40mail.gmail.com >>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOcELL8wEy1NrdM10dd9xPmBmrUuy8CrV95eHoOwdg_TzhmLnw%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- -- v8-dev mailing list v8-dev@googlegroups.com http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/v8-dev/CABc02_KD_3Krg2UdLKU6iSv%3Dy2wQoqznrBZG1xU6CV7wWkj6MA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
