Re: [charmod-norm] Various Editorial Suggestions

1: Done
2: This is a good suggestion, but I thought the wording ended up a bit strange. I applied a deeper edit:

>  Some characters used in this document's examples might not appear as intended on your specific device or display. Usually this is due to lack of a script-specific font installed locally or due to other limitations of your specific rendering system. This document uses a Webfont to provide fallback glyphs for many of the non-Latin characters, but your device might not support displaying the font. To the degree possible, the editors have tried to ensure that the examples nevertheless remain understandable.

I noticed (actually, it's been burning in my mind for a while) that we don't define "code point" any where, even though we use the term liberally. I added a definition of code point:

> A <dfn data-lt="Unicode code point|code point|code points">Unicode code point</dfn> (or "code point") refers to the numeric value assigned to each Unicode character. Unicode code points range from 0 to 0x10FFFF<sub>16</sub>. (See Section 4.1 in [[!CHARMOD]] for a deeper discussion of character encoding terminology.)

3. Ugh. Done.

4. Done.

5. Amusingly, ASCII and ISO/IEC 646 aren't in Specref. I don't really want to reference RFC20. I copied in the ref from Charmod. As part of this, I notice that specref no longer supports the `note` feature, which we used in some of our references. I will follow up on that separately.

6. I replaced the two occurrences of "logical character" with "abstract character" (and some rewriting in both places).

7. Agreed. I didn't do that work yet and will create a separate issue for the necessary PR.

8. Done.

9. Done.

10. A wildebeest puts... never mind... Done (the wildebeest reference will have to be explained in teleconference)

11. Done.

12. Fixed. I converted the parenthetical to a separate sentence (An example of this...) since the sentence is followed by a parenthetical sentence.

Thank you for the review!!





-- 
GitHub Notification of comment by aphillips
Please view or discuss this issue at https://github.com/w3c/charmod-norm/issues/154#issuecomment-353656891 using your GitHub account

Received on Friday, 22 December 2017 18:59:50 UTC