I'm not sure if this is something Globalize.js wants to tackle, but it would be great to have Break Iteration support for text boundary analysis based off ICU's break iterator. Particularly useful would be the ability for Globalize.js to give developers the ability to detect word boundaries or manage layout problems with complex text layout languages (Southeast Asia: Burmese, Khmer, Lao, Thai).
By being able to iterate through the content, developers can then provide support for platforms that lack that support (Firefox for instance). I worked with the team that helped supply the data for Lao break iteration and helped support the person who helped with Burmese. I am also somewhat familiar with both Thai and Khmer. Let me know if I can help in any way if you all decide to take this on.
I'm not sure if this is something Globalize.js wants to tackle, but it would be great to have Break Iteration support for text boundary analysis based off ICU's break iterator. Particularly useful would be the ability for Globalize.js to give developers the ability to detect word boundaries or manage layout problems with complex text layout languages (Southeast Asia: Burmese, Khmer, Lao, Thai).
By being able to iterate through the content, developers can then provide support for platforms that lack that support (Firefox for instance). I worked with the team that helped supply the data for Lao break iteration and helped support the person who helped with Burmese. I am also somewhat familiar with both Thai and Khmer. Let me know if I can help in any way if you all decide to take this on.