You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a matter of fact, yes. The awesome and talented @radzinzki may work on porting some or all of those in the future. The biggest obstacle we face is getting all the unicode data into Javascript land. As @radzinzki discovered while porting text segmentation (see #47), the combined metadata for each character in unicode can take up quite a bit of space (on the order of 2mb) and is therefore not suitable for transmission to a browser. He's working on a way to better compress the data, which should enable us to continue porting additional twitter-cldr-rb features.
It's worth noting that, even if we can compress unicode metadata effectively, we likely will not be able to do so with collation data due once again to size constraints (collation data weighs in at 5mb). Case folding and normalization may be possible.
Thanks for the kind words, @camertron. Collation an the other features are in my to-do list and I hope to get to them soon. As @camertron said, bundle size is an important factor to be considered. If the data is too big and can't be effectively compressed, collation could be an opt-in plug in.
twitter-cldr-rb do have support for case folding, normalization and collation. Are there plans to port these features into twitter-cldr-js as well ?
The text was updated successfully, but these errors were encountered: