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/09/03 16:14] rsewikiadmin |
design:text-requirements [2013/10/15 19:52] (current) paul |
||
---|---|---|---|
Line 1: | Line 1: | ||
==== Requirements for Text Output ==== | ==== Requirements for Text Output ==== | ||
- | Technical requirements: | + | The following assumes that the text-only non-canonical |
- | The .txt publication | + | |
- | * use classic/ | + | |
- | * have paginated output | + | |
- | * use classic/ | + | |
- | * support UTF-8 encoding | + | |
+ | The text-only format must have the same page height limitations as the current RFC format. | ||
- | Policy requirements: | + | The text-only format must allow for preformatted text and art to be 80 characters wide without wrapping those lines. |
- | * an RFC may include ASCII art OR SVG, but not both | + | |
- | * the .txt publication output will include links to the info pages where there are images | + | |
- | * we could potentially include direct links to the HTML anchors, but am concerned about future failure | + | |
- | * non-ASCII characters in the Author' | + | |
+ | 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. |