This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
design:text-requirements [2013/09/03 13:33] rsewikiadmin created |
design:text-requirements [2013/10/15 19:52] (current) paul |
||
---|---|---|---|
Line 1: | Line 1: | ||
==== Requirements for Text Output ==== | ==== Requirements for Text Output ==== | ||
- | - ASCII vs UTF-8 | + | 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. |
- | - Paragraphs breaking across pages vs possibly-large whitespace at the bottom | + | |
- | - Classic | + | 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. | ||
+ | |||
+ | The text-only format must represent all SVG-based artwork as a "see reference" | ||
+ | |||
+ | 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. |