Markus Scherer

Note that this sort of feature needs a fair bit more code than just a Collator, and you can't just build it on top of compare(). You basically need to...

> This PR still has a bunch of "FYI" comments in it, which I assume you don't intend. Is it actually ready for review? We thought that it's ok for...

> So do you just want the normative parts reviewed at the moment? Also, do you intend to address the TODOs before review? Some of them look like they'd be...

> What is `\q`? The [proposal readme doesn't say](https://github.com/tc39/proposal-regexp-set-notation), I don't recall it being presented, and neither the [google doc](https://docs.google.com/document/d/1Tbv3hfX9CxQtzH9r-JdxJsQZhmmDsidRUKKxg345JV0/edit#) nor this PR give it any semantics. We flip-flopped on...

> Can the new table be dropped in light of #2649? No. That PR replaces tables of Unicode property *values* with a reference to where Unicode defines those. That works...

AFAICT we have taken care of all of the feedback, except for editorial issues (naming, strings vs. sequences) that I hope won't block moving to stage 3. PTAL.

> > What’s the timeline on getting the accepted proposal reflected “on paper” in the Unicode Standard? > > Not sure. @markusicu could probably answer. I was just going to...

> > > What’s the timeline on getting the accepted proposal reflected “on paper” in the Unicode Standard? > > > > > > Not sure. @markusicu could probably answer....

I feel pretty strongly that this WG, and the CLDR spec portion that it is tasked to produce, **should not** define a resource file format. This WG should define a...

I don't know what the question is here. If you provide a literal value that contains line feeds, then it contains line feeds. That may be desirable, or it may...