User Tools

Site Tools


design:utf-8

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:utf-8 [2013/10/15 12:30]
rsewikiadmin
design:utf-8 [2019/10/07 12:10] (current)
rsewikiadmin
Line 1: Line 1:
 +If RFCs-to-be come in with internationalized characters (e.g., in name, postal address, example), the expectatin is to ask the i18n directorate for review assistance. If that is not possible, either because the review team has closed and/or is unable to complete a review, the first step will be to reach out to the Apps ADs for assistance, and if they have no guidance or is unresponsive, send a request for assistance to the rfc-interest mailing list. 
 +
 +
 Some discussion of requirements, goals, and desires around non-ASCII characters are at https://www.rfc-editor.org/rse/wiki/doku.php?id=formatreq. Some discussion of requirements, goals, and desires around non-ASCII characters are at https://www.rfc-editor.org/rse/wiki/doku.php?id=formatreq.
 The table below summarizes a taxonomy of cases where (non-ASCII) UTF-8 might or might not be allowed, along with some thoughts. The intent is that each row represents a separate policy decision. The table below summarizes a taxonomy of cases where (non-ASCII) UTF-8 might or might not be allowed, along with some thoughts. The intent is that each row represents a separate policy decision.
Line 5: Line 8:
  
 ^ Case ^ Section ^ Use ^ Consensus ^ Comments ^ ^ Case ^ Section ^ Use ^ Consensus ^ Comments ^
-| 1a | (title page) | Author name | Yes| Answer should match (6a) | +| 1a | (title page) | Author name | Yes | Answer should match (6a) | 
-| 1b | (title page) | Author affiliation | | Answer should match (6b) | +| 1b | (title page) | Author affiliation | Yes | Answer should match (6b) | 
-| 1c | (title page) | Document title | | | +| 1c | (title page) | Document title | No? | | 
-| 2 | Abstract | Prose | | Could be same as (3e), but Abstracts may also be separately compiled into other indices so could have a different answer ​| +| 2 | Abstract | Prose | No? | Could be same as (3e), but Abstracts may also be separately compiled into other indices so could have a different answer ​| 
-| 3a | Body or Appendix | Example string | | E.g. fictional person name, IRI, EAI, domain name, etc. Currently there's no XML markup to denote example strings, so hard to distinguish from (3c) | +| 3a | Body or Appendix | Example string | Yes | E.g. fictional person name, IRI, EAI, domain name, etc. Currently there's no XML markup to denote example strings, so hard to distinguish from (3c) | 
-| 3b | Body or Appendix | Code snippet | | | +| 3b | Body or Appendix | Code snippet | No? "Code" does not mean examples here, but actual grammar like ABNF, C, etc. 
-| 3c | Body or Appendix | Literal protocol element | | Required transliteration should use U+xxxx syntax | +| 3c | Body or Appendix | Literal protocol element | Yes? | Required transliteration should use U+xxxx syntax | 
-| 3d | Body or Appendix | Document title of a cited document | | Answer should match (4c) | +| 3d | Body or Appendix | Document title of a cited document | Yes | Answer should match (4c) | 
-| 3e | Body or Appendix | Prose | No| e.g. use of "naïve" in http://tools.ietf.org/html/rfc4690#section-1.5.5 | +| 3e | Body or Appendix | Prose | No | e.g. use of "naïve" in http://tools.ietf.org/html/rfc4690#section-1.5.5 | 
-| 3f | Body or Appendix | Section title | | | +| 3f | Body or Appendix | Section title | No? | | 
-| 4a | References | Author name | Yes| Answer should match (1a) | +| 4a | References | Author name | Yes | Answer should match (1a) | 
-| 4b | References | Author affiliation | | Answer should match (1b) | +| 4b | References | Author affiliation | Yes | Answer should match (1b) | 
-| 4c | References | Document title | | Not necessarily an RFC that's being referenced | +| 4c | References | Document title | Yes | Not necessarily an RFC that's being referenced | 
-| 4d | References | Document IRI | No| | +| 4d | References | Document IRI | No | | 
-| 5a | Acknowledgements | Person name | Yes| | +| 5a | Acknowledgements | Person name | Yes | | 
-| 5b | Acknowledgements | Organization name | | | +| 5b | Acknowledgements | Organization name | Yes | | 
-| 6a | Authors Addresses | Author name | Yes| |  +| 6a | Authors Addresses | Author name | Yes | |  
-| 6b | Authors Addresses | Author affiliation | | |      | +| 6b | Authors Addresses | Author affiliation | Yes | |      | 
-| 6c | Authors Addresses | Author email address (EAI) | | | +| 6c | Authors Addresses | Author email address (EAI) | No? | | 
-| 6d | Authors Addresses | Author IRI | No| | +| 6d | Authors Addresses | Author IRI | No | | 
-| 6e | Authors Addresses | Author postal address | | | +| 6e | Authors Addresses | Author postal address | Yes | | 
-| 7a | (page footer) | Author surname | | | +| 7a | (page footer) | Author surname | Yes? | | 
-| 7b | (page header) | Abbreviated document name | | | +| 7b | (page header) | Abbreviated document name | No? | | 
-| 8a | (metadata) | Keywords | | |+| 8a | (metadata) | Keywords | Yes | |
 | |
  
design/utf-8.1381865453.txt.gz · Last modified: 2013/10/15 12:30 by rsewikiadmin