I expected the Intl.Segmenter to behave based on the provided locale parameter and some dictionary per it. However there seems to be no change in behavior depending on the locale, and only the basic algorithm specified in Unicode is implemented.
So there's no reason why I couldn't completely polyfill it. It still has a chance to be useful for Korean, unlike other CJK, it has strict word spacing.
I expected the
Intl.Segmenter
to behave based on the providedlocale
parameter and some dictionary per it. However there seems to be no change in behavior depending on the locale, and only the basic algorithm specified in Unicode is implemented.So there's no reason why I couldn't completely polyfill it. It still has a chance to be useful for Korean, unlike other CJK, it has strict word spacing.