This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
design:formats [2013/09/06 07:12] tony [Avoiding Bad Breaks in Paginated Text] |
design:formats [2013/10/15 14:45] rsewikiadmin |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Thoughts on Non-Canonical Formats ====== | ====== Thoughts on Non-Canonical Formats ====== | ||
- | |||
This page is for keeping thoughts about the expected output formats *other than* XML. | This page is for keeping thoughts about the expected output formats *other than* XML. | ||
Line 7: | Line 6: | ||
* Well-structured HTML | * Well-structured HTML | ||
- | * Unpaginated text | + | * Text (Unpaginated text and Paginated text) |
- | * Paginated text | + | |
* EPUB | * EPUB | ||
Line 14: | Line 12: | ||
===== Well-structured HTML ===== | ===== Well-structured HTML ===== | ||
- | A strong design goal is that the conversion from canonical XML to HTML should be round-trippable, | + | Initial proposal: |
+ | Response: | ||
+ | * Round-tripping would require preserving non-semantic information. | ||
+ | * For instance, it'll be hard not no loose information from < | ||
+ | * If roundtripping is not a goal, we need to make clear what kind of information we want to be represented in the HTML. "All semantic content" | ||
+ | * Semantic information *will* be lost during the transformation. The balancing act is making certain that enough semantic information is kept for making the HTML output useful for html-processing tools. The tough part is how to express that as a requirement. | ||
- | < | + | For the example of counter=" |
+ | | ||
+ | | ||
+ | when the namespace characters are different. (What do you do with a | ||
+ | | ||
+ | | ||
+ | down. But is it the type of semantic information that *needs* to be | ||
+ | | ||
- | ===== Unpaginated Text ===== | + | Initial proposal: Consider allowing (eventually) javascript |
- | See [[design:text-sample|]] | + | Response: No |
+ | * This would negatively impact people feeling safe when opening RFCs | ||
+ | * Would make it more difficult to ensure RFCs look the same in all environments | ||
+ | * We wouldn' | ||
+ | * It's completely unnecessary for a simple | ||
+ | * Think of the testing involved. | ||
- | ===== Paginated Text ===== | ||
- | This is text with headers, footers, and page break characters. | + | ===== Text ===== |
+ | |||
+ | Initial proposal: There should be multiple | ||
+ | |||
+ | Response: Limit the .txt output to one option only, as similar as reasonable to what is available today. | ||
==== Avoiding Bad Breaks in Paginated Text ==== | ==== Avoiding Bad Breaks in Paginated Text ==== | ||
Line 37: | Line 55: | ||
===== PDF ===== | ===== PDF ===== | ||
- | There will be (at least) two formats | + | Initial proposal: The document needs to include live links |
+ | For linking between RFCs, pointers to RFCs published before the format switchover will point to the TXT version | ||
+ | For linking between RFCs, pointers to RFCs published after the format switchover will point to the PDF version and will allow for pointers to specific sections within a document | ||
+ | The PDF version will include the standard front page header and include page numbers | ||
+ | The PDF version | ||
- | * PDF format 1 that looks much like how the HTML would look if printed, including having live links, text formatting | + | Response: With HTML as an option, there is not a compelling case to require links in the PDF. One use case described was that of the IESG, several members of which choose to print out the PDF version for review. |
- | * PDF format 2, hopefully having live links but //not// having text formatting or SVG art. | + | |
- | Both PDF formats are produced for US Letter and A4 page sizes. | + | Team also briefly considered how a tool like [[http:// |
- | + | ||
- | We have talked about using [[http:// | + | |
===== EPUB ===== | ===== EPUB ===== | ||
If we also want to do MOBI (the native Amazon format), we might consider running the free-but-closed-source program from Amazon [[http:// | If we also want to do MOBI (the native Amazon format), we might consider running the free-but-closed-source program from Amazon [[http:// | ||
+ | |||
+ | If the HTML output is designed well, it can be used to create EPUB output with few, if any, additional requirements. | ||