This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
design:text-requirements [2013/10/09 13:55] paul Moved the ASCII stuff to the end |
design:text-requirements [2013/10/15 19:52] (current) paul |
||
---|---|---|---|
Line 1: | Line 1: | ||
==== Requirements for Text Output ==== | ==== Requirements for Text Output ==== | ||
- | The following assumes that there is going to be only one text-only non-canonical format, that its intended consumer is people who like the current format but want to be able to get all the semantic content out of the new canonical format, and that the HTML format will be done in a way where copy-and-paste of text will be easy and predictable. | + | The following assumes that the text-only non-canonical format intended consumer is people who like the current format but want to be able to get all the semantic content out of the new canonical format, and that the HTML format will be done in a way where copy-and-paste of text will be easy and predictable. |
- | The text-only format must have the same page height limitations as the current RFC format. It must contain the same headers and footers and page break character as the current RFC format. There is no requirement that the text-only format use widow and orphan control; the use case for this is to allow similar referencing of paragraphs from the text-only format to the canonical format and non-canonical HTML format. | + | The text-only format must have the same page height limitations as the current RFC format. |
- | The text-only format must allow for preformatted text and art to be 80 characters wide without wrapping those lines. This is due to the relaxation of the 72-character restriction on preformatted text and art in the new canonical format. | + | The text-only format must allow for preformatted text and art to be 80 characters wide without wrapping those lines. |
- | The text-only format must represent all SVG-based artwork as a "see reference" | + | The text-only format must represent all SVG-based artwork as a "see reference" |
- | + | ||
- | === ASCII vs. UTF-8 for Text Output === | + | |
- | + | ||
- | As of 2013-10-09, it is not clear whether or not the text output will be ASCII or UTF-8. The following assumes ASCII. If the format is UTF-8, then the following is wrong. | + | |
- | + | ||
- | The text-only format must have the same character-set limitations as the current RFC format. For new RFCs that have non-ASCII characters in them, each such character must be represented as // | + | |
- | //Dave thinks: disagree with the above paragraph. I'm leaning towards saying there should be a separate UTF-8 (e.g. .utf8) text version. | + | |
+ | The RFC Editor must list all of the changes from the current RFC format to the new text format in a single document that can be used by people who have written text-processing tools. | ||
+ | After the RFC Editor has made the cut-over to the new canonical format (and thus the new non-canonical text-only format), all RFCs with a higher number must be in the new format. |