This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
design:utf8-requirements [2013/11/05 10:38] rsewikiadmin |
design:utf8-requirements [2013/11/06 18:12] rsewikiadmin |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | All documents will be UTF-8 encoded and MUST apply Normalization Form C to all metadata fields such as document name, authors, and references unless a specific exception | + | Author names: Valid Unicode is required, and for non-ASCII names, an ASCII-only identifier |
+ | |||
+ | Bibliographic text: The reference must point to something that has been translated to English; whatever subfields | ||
+ | are present MUST be available in ASCII (translated to English when appropriate). | ||
+ | |||
+ | Keywords: US-ASCII only | ||
+ | |||
+ | Body: The mention of non-ASCII characters | ||
+ | |||
+ | 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 as the body. If it is sensible (i.e., more understandable for a reader) for a given document | ||
+ | |||
+ | 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 forms: If the normalization matters to the content, the authors must submit in a normalization-resistant form. Do not expect normalization forms to be preserved. | ||
+ | |||
+ | Codepoint numbers (" | ||
+ | Delta" | ||
All documents should identify themselves as being UTF-8. | All documents should identify themselves as being UTF-8. |