User Tools

Site Tools


design:utf8-requirements

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
design:utf8-requirements [2013/11/06 13:04]
rsewikiadmin
design:utf8-requirements [2013/11/06 18:40] (current)
rsewikiadmin
Line 2: Line 2:
 Author names: Valid Unicode is required, and for non-ASCII names, an ASCII-only identifier is required. Author names: Valid Unicode is required, and for non-ASCII names, an ASCII-only identifier is required.
  
-Bibliographic text: The reference must point to something that has been translated to English; whatever subfields +Bibliographic text: The reference ​entry must be in English; whatever subfields are present MUST be available in ASCII.  As long as good sense is used, they MAY also include ​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, they 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,   We would NOT apply in the use case and we WOULD apply in the mention case.  So,
Line 20: Line 19:
 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 ("​U+0394"​) and Unicode character names ("​Greek Capital Letter  
 +  Delta"​) are normalization-resistant forms. ​ The characters themselves may not be.
  
  
design/utf8-requirements.1383771861.txt.gz · Last modified: 2013/11/06 13:04 by rsewikiadmin