design:utf8-requirements
Differences
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 12:05] 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. This applies to both normative and informative references. | + | are present MUST be available in ASCII (translated to English when appropriate). As long as good sense is used the subfields MAY also appear in non-ASCII characters at author discretion. This applies to both normative and informative references. |
| Keywords: US-ASCII only | Keywords: US-ASCII only | ||
| - | Body: The mention of non-ASCII characters requires identifiers, encourage characters, allow unicode names. (Note: use versus mention distinction) | + | Body: The mention of non-ASCII characters requires Unicode code points, encourage characters, allow Unicode character names. General use does not require any clarifying identifiers or Unicode names. (Note: use versus mention distinction) |
| + | |||
| + | We would NOT apply in the use case and we WOULD apply in the mention case. So, | ||
| + | CATEGORY NUMBER | ||
| + | naïve 300 | ||
| + | but | ||
| + | CATEGORY EXAMPLES | ||
| + | Latin naïve (U+0063 U+0061 U+00EF U+0076 U+0065) | ||
| 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. | + | Codepoint numbers ("U+0394") and Unicode character names ("Greek Capital Letter |
| + | Delta") are normalization-resistant forms. The characters themselves may not be. | ||
design/utf8-requirements.txt · Last modified: 2013/11/06 18:40 by rsewikiadmin
Page Tools
