There are some Mozillans who attend our monthly ECMA-402 calls, and they've signed off on the latest version of Intl.Segmenter. The spec is written such that it's not necessary to use ICU as the breaking engine, and IIRC, the intl team at Mozilla got approval to add in the segmentation data if they decide to go the ICU route.
On Thu, Aug 13, 2020 at 4:19 AM Emilio Cobos Álvarez <[email protected]> wrote: > > On 8/13/20 12:17 AM, Frank Tang wrote: > > [Note: Resent due to message header problem. Sorry] Contact emails > [email protected], [email protected] > > Explainer > https://github.com/tc39/proposal-intl-segmenter > > Specification https://tc39.github.io/proposal-intl-segmenter/ > > Design docs > > https://docs.google.com/document/d/1xugLpLmgRFnNXK8ztariTAbD2IXueDw1T3VNuuZCz8k/edit#heading=h.xgjl2srtytjt > > https://docs.google.com/presentation/d/1X2zBU3bZ4ergVMWfubCsdnHFzeaDgqiTRJVgvNGjQBs/edit#slide=id.p > > TAG review review by ECMA402 > > Summary Intl.Segmenter implements methods for finding the location of > boundaries in text, including grapheme, line, word and sentence boundary > analysis. > > Motivation Currently, chrome is shipped with Intl.v8BreakIterator - a non > standard way for similar functionality. According to > https://www.chromestatus.com/metrics/feature/timeline/popularity/556 on > 2020 Feb there are 0.74% of the web page use it. Intl.Segmenter is the web > standard to replace it. > > Risks > > > Interoperability and Compatibility The specification is moved to Stage 3 > in TC39 2020-Jul meeting with support from ECMA402. > > *Gecko*: In development ( > https://bugzilla.mozilla.org/show_bug.cgi?id=1423593) > > FWIW, in development seems a bit of a stretch since there hasn't been > activity in the bug for a while. > > The patch is three years old and there was a bit of a concern due to the > binary size growing quite a bit > <https://bugzilla.mozilla.org/show_bug.cgi?id=1423593#c9>. > > (Not an expert on this, but Gecko's layout engine doesn't use ICU for > line-breaking, IIRC, so a lot of the ICU data that would be required for > this has to be imported). > > There may be alternative implementation strategies or what not, but it > doesn't seem to be actively worked on. > > > *WebKit*: No signal > > *Web developers*: No signals > > Ergonomics Engineer from Apple believe we should not add line break > support to the Intl.Segmenter because the developer may abuse the API and > perform text layout by themselves instead of depending on CSS. The line > break feature then were removed from the specification in the current shape. > > > 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> > ? Yes https://github.com/tc39/test262/tree/master/test/intl402/Segmenter > > Link to entry on the Chrome Platform Status > https://www.chromestatus.com/feature/6099397733515264 > > This intent message was generated by Chrome Platform Status > <https://www.chromestatus.com/>. > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOcELL-m7DZ5OAwZj9FqX9VKZKWYd_Qf0YeaXCs3YAEbcnPsKA%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOcELL-m7DZ5OAwZj9FqX9VKZKWYd_Qf0YeaXCs3YAEbcnPsKA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > -- -- v8-dev mailing list [email protected] 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/v8-dev/CABxsp%3DmU7Nk%2BVH%3Dkd7s43t-cWqjZcqCUPtsL5WzV%3D7E15GxjqQ%40mail.gmail.com.
