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/10/04 15:05] paul Removed link from ASCII link example |
design:text-requirements [2013/10/09 13:57] paul Added Paul comments |
||
---|---|---|---|
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 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. | ||
Line 6: | Line 6: | ||
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. 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 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 // | 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 // | ||
- | The text-only format must represent all SVG-based artwork as a "see reference" | + | //Dave thinks: disagree with the above paragraph. I'm leaning towards saying there should be a separate UTF-8 (e.g. .utf8) |
+ | //Paul thinks: if there are two versions, the .txt should be UTF-8 and the ASCII version should be .asc. If there is an all-ASCII version, we need to ask the authors how they want their names (mis)spelled in ASCII.// | ||