Shane F. Carr

We are now considering this blocked on #2127

Intl.Segmenter is in scope for 402, and I think it makes sense to include here in ICU4X as well. I think we should build the segmenter based on the unicode...

Adding to backlog along with Normalization (#40).

@methyl compiled ICU4C Segmenter to WebAssembly as a polyfill for Intl.Segmenter: https://github.com/surferseo/intl-segmenter-polyfill According to https://github.com/tc39/proposal-intl-segmenter/issues/118#issuecomment-645238037, the .wasm file is ~350 KB gzipped, with the Thai dictionary but not the other...

One of the main value propositions of ICU4X is to provide Unicode and CLDR data (#217 is a thread specifically about Unicode character property data). In cases where functionality is...

CC @nathanhammond

Implementation feedback from @aheninger: > Here are a few followup comments to the ICU4X deep dive discussion of April 21. > > 1. Testing. For evaluating uax14_rs (or other new...

See some benchmark results from @aethanyc in https://github.com/unicode-org/icu4x/issues/707.

This will be closed after segmenter moves to components in #2259.

Previously discussed in https://github.com/unicode-org/icu4x/issues/424 and fixed in https://github.com/unicode-org/icu4x/pull/616