Shane F. Carr

@FrankYFTang

@FrankYFTang Have you followed up with Mark about this in the CLDR spec?

> @sffc any action items on how to move this forward? Status is "help wanted". It just needs a champion.

Proposal please, simply because it makes it a lot easier to track and organize. I think we can probably get this directly to Stage 2 or 3 in a single...

Yes, the code you wrote is the currently recommended pattern. Since both Intl Enumeration and Intl DisplayNames are relatively new APIs, additional real-world experience will be helpful to learn how...

The use case comes from a Google team that is implementing a spell checker via word segmentation. > We want to detect URLs as a whole so that we can...

I agree that we don't want an explosion of options for each edge case. I think we could look at use cases, though, and center options around those use cases....

TG2 discussion: https://github.com/tc39/ecma402/blob/master/meetings/notes-2022-03-17.md#intlsegmenter-with-urls-email-addresses-and-acronyms Conclusion: - FYT to investigate the V8 change - Come back to this group if necessary

Another TC39-TG2 discussion: https://github.com/tc39/ecma402/blob/master/meetings/notes-2022-06-16.md#intlsegmenter-with-urls-email-addresses-and-acronyms-656 We agree that this is a bug in Chrome, but there could be phrasing improvements in UTS-35 as well as additional tests in Test262.

@macchiati says to fill in the form at https://corp.unicode.org/reporting/error.html with suggestions. He says that it may be useful to investigate the `@` symbol. He says: > BTW, @ might be...