This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
design:text-requirements [2013/09/03 16:22] rsewikiadmin |
design:text-requirements [2013/10/09 13:57] paul Added Paul comments |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ==== Requirements for Text Output ==== | + | ==== Requirements for Text Output ==== |
- | Technical requirements: | + | The following assumes that there is going to be only one 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. 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. | ||
- | Policy requirements: | + | 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 |
- | * 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" | ||
- | Current requirements re: page breaking | + | === ASCII vs. UTF-8 for Text Output === |
- | #172: page-breaking enhancements | + | 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 |
- | Improve the PI autobreaks=" | + | |
- | - the middle | + | |
- | | + | |
- | | + | |
- | | + | |
- | doesn' | + | |
- | Ticket URL: <http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/ | + | 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 //[*U+xxxx*]//, |
+ | //Dave thinks: disagree with the above paragraph. I'm leaning towards saying there should be a separate UTF-8 (e.g. .utf8) text version. | ||
- | Current internal guidance to the RPC: | + | //Paul thinks: if there are two versions, |
- | + | ||
- | "3+ lines held together" | + | |
- | Keep a section title with the first 3 lines of the section. | + | |
- | Keep a figure on one page. This includes its title (if any). | + | |
- | - if figure does not fit on one page, break between discrete items in the figure. | + | |
- | Keep a table on one page. This includes its title (if any). | + | |
- | - if table does not fit on one page, break between rows. | + | |
- | Keep a term with its definition. | + | |
- | - if definition is long (over 5 lines), keep at least the first 3 lines of the definition with the term. | + | |
- | Keep a given reference on one page. | + | |
- | Start Appendix A on a new page. | + | |
- | + | ||
- | More subjective: | + | |
- | Keep intro text with what it's introducing. | + | |
- | Break pseudocode nicely. | + | |