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/06 13:53] rsewikiadmin |
design:utf8-requirements [2013/11/06 18:12] rsewikiadmin |
||
---|---|---|---|
Line 3: | Line 3: | ||
Bibliographic text: The reference must point to something that has been translated to English; whatever subfields | 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), as long as good sense is used, they MAY also appear in non-ASCII characters at author discretion. | + | are present MUST be available in ASCII (translated to English when appropriate). As long as good sense is used the subfields |
Keywords: US-ASCII only | Keywords: US-ASCII only | ||
- | Body: The mention of non-ASCII characters requires | + | Body: The mention of non-ASCII characters requires |
We would NOT apply in the use case and we WOULD apply in the mention case. So, | We would NOT apply in the use case and we WOULD apply in the mention case. So, | ||
Line 20: | Line 20: | ||
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 | 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. |
+ | |||
+ | Codepoint numbers (" | ||
+ | Delta" | ||