This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
design:utf8-requirements [2013/10/15 14:23] rsewikiadmin created |
design:utf8-requirements [2013/11/06 18:40] (current) rsewikiadmin |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | All documents will be UTF-8 encoded | + | Author names: Valid Unicode is required, and for non-ASCII names, an ASCII-only identifier is required. |
+ | |||
+ | Bibliographic text: The reference entry must be in English; whatever subfields are present MUST be available in ASCII. | ||
+ | |||
+ | Keywords: US-ASCII only | ||
+ | |||
+ | Body: The mention of non-ASCII characters requires Unicode code points, encourage characters, allow Unicode character names. | ||
+ | |||
+ | We would NOT apply in the use case and we WOULD apply in the mention case. So, | ||
+ | CATEGORY | ||
+ | naïve | ||
+ | but | ||
+ | | ||
+ | Latin | ||
+ | |||
+ | Tables: Tables follow the same rules for identifiers and characters | ||
+ | |||
+ | U+ notation must be used except within a code component where you must follow the rules of the programming language in which you are writing the code | ||
+ | |||
+ | Normalization | ||
+ | |||
+ | Codepoint numbers (" | ||
+ | Delta" | ||
+ | |||
+ | |||
+ | All documents should identify themselves as being UTF-8. | ||
| | ||
- | | + | An implementer must be able to implement the specification without any confusion or ambiguity introduced by the use of UTF-8 rather than ASCII. |
| | ||
- | Must be able to reference (cite) the document | + | People must be able to reference (cite) the RFC from elsewhere in a standard way, including from documents that only support ASCII. |
| | ||
- | Must be able to reference (cite) other documents in an unambiguous way. | + | The RFC must be able to reference (cite) other documents in an unambiguous way. |
| | ||
- | | + | Cross-references (including references to other documents) must be unambiguous even from a printed document. |
| | ||
- | Must be able to index the document | + | Tools must be able to index the RFC in various ways, so searching |