r12a

@huijing it's a while since i worked on the clreq source so, to refresh my memory, i reorganised the markup as i think it should be. This may save you...

> Based on discussion during the CLReq call on 17 Nov, the team feels that the term "inline annotation" would be appropriate instead of using "warichū" I have no problem...

_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...

_The first comment in this issue contains text that will automatically appear in one or more gap-analysis documents as a subsection with the same title as this issue. Any edits...

_The first comment in this issue contains text that will automatically appear in [the clreq gap-analysis document](https://www.w3.org/International/clreq/gap-analysis/#lists) as a subsection with the same title as this issue. Any edits made...

> @r12a How to add this to the Gap-analysis pipeline? It's already there, but only in the editor's version. You need to publish the doc to /TR using echidna once...

@xfq Could you add a brief description of what the spec has support for (maybe just one sentence will suffice, but it's good to indicate the basis on which this...

Btw, i think this issue probably also applies to Thai and other scripts that don't use space as a word-separator, not just C&J. And you should probably create a stub,...

Or say "2 em-space characters".

Just noticing this thread now. (For future reference, @ianbjacobs and others, note that if you stick the i18n-tracker label on an issue, the i18n WG will be notified about it...