r12a

Interestingly, and by coincidence, the Unicode Editorial Committee discussed this same topic wrt Unicode publications last week. Their approach, which they are not planning to change, is to limit the...

Here's what occurred to me. I was surprised that you'd managed to squeeze this in between the abstract and SOTD. While that seems appropriate, unfortunately it looks a bit odd...

For the Khmer lreq doc i experimented with putting the acknowledgments section at the beginning of the introduction, and calling it 'Contributors'. It seems not so bad... https://w3c.github.io/sealreq/khmer/indexnew

Link broken. Need to check with PhilA.

[from Addison] This issue called for the incorporation of guidence found in “Data for the Web: Best Practices” [DWBP][7]. Starting from the text found there, I reworded to suit this...

How about "When defining internal data formats,..." ?

Mm. For me 'internal' doesn't exclude what's interchanged. How about "When defining data format representations that are used internally or for data interchange, ..." ?

As you said, not for presentation, but defining it that way is a little bit of a round about way of talking. I was hoping we could more directly express...

A quicker way to create and run tests for this is to send the characters to my font lister, eg. https://r12a.github.io/scripts/fontlist/?script=hans&text=%E2%80%A6%E4%B8%80%E2%8B%AF#result That shows several fonts that you don't mention but...

_The first comment in this issue contains text that will automatically appear in [the Chinese gap-analysis document](https://w3c.github.io/clreq/gap-analysis/) as a subsection with the same title as this issue. Any edits made...