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 15:54]
dthaler
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 10: Line 13:
 | 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 ​| | 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 | 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) | | 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 | No | "Code" does not mean examples here, but actual grammar like ABNF, C, etc. |+| 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 | Yes? | 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 | Yes | Answer should match (4c) | | 3d | Body or Appendix | Document title of a cited document | Yes | Answer should match (4c) |
design/utf-8.1381877654.txt.gz · Last modified: 2013/10/15 15:54 by dthaler