This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
design:utf8-requirements [2013/11/06 12:05] rsewikiadmin |
design:utf8-requirements [2013/11/06 13:53] rsewikiadmin |
||
---|---|---|---|
Line 7: | Line 7: | ||
Keywords: US-ASCII only | Keywords: US-ASCII only | ||
- | Body: The mention of non-ASCII characters requires identifiers, | + | Body: The mention of non-ASCII characters requires identifiers, |
+ | |||
+ | 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 to have two tables, one including the identifiers and characters, one with just the characters, that will be allowed on a case by case basis. | 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 to have two tables, one including the identifiers and characters, one with just the characters, that will be allowed on a case by case basis. | ||
- | U+ except within a code component where you must follow the rules of the programming language in which you are writing the code | + | 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. | 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. |