RSE Wiki Archive

User Tools

Site Tools

Trace:
design:formats

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision 		Previous revision
Next revision Both sides next revision
design:formats [2013/08/16 16:23]
paul created 		design:formats [2013/10/01 23:42]
rsewikiadmin [PDF] changed requirements based on list discussion and professional opinion
Line 14: Line 14:
 ===== Well-structured HTML ===== ===== Well-structured HTML =====
  
-<del>Joe goes here.</del>+A strong design goal is that the conversion from canonical XML to HTML should be round-trippable, that is, that it should be possible to convert the HTML back to XML with literally zero loss of semantic content. Conversion from and to the canonical XML might be done with XSLT. 
 + 
 +<del>Joe says more here.</del>
  
 ===== Unpaginated Text ===== ===== Unpaginated Text =====
 +See [[design:text-sample|]]
  
 ===== Paginated Text ===== ===== Paginated Text =====
  
-A way to eliminate the need for widow/orphan control or bad page breaks in figures is to just be willing to leave extra white space at the bottom of the paginated pages. If a single paragraph or figure is too large to fit on a paginated page (the tool should warn about this every time it emits paginated text output), the Production Center can break the paragraph or split the figure into two.+This is text with headers, footers, and page break characters.
  
-===== PDF =====+==== Avoiding Bad Breaks in Paginated Text ====
  
-We have talked about using [[http://www.princexml.com|PrinceXML]] to generate PDF. +The paginated text format needs to deal with the issue of paragraph or art that would be split over a page break. 
  
-We need to have at least two formats: US-standard (8.5 x 11) and A4.+[PH] Eliminate the problem is to just be willing to leave extra white space at the bottom of the paginated pages. If a single paragraph or figure is too large to fit on a paginated page (the tool should warn about this every time it emits paginated text output), the Production Center can break the paragraph or split the figure into two. 
 + 
 +[TH] (widow == bottom line of a paragraph that winds up in the next column/page. orphan == top line of a paragraph that is separated from the rest of the paragraph by a column/page break.) In most cases, both can be eliminated by not limiting yourself to a strict number of lines (N) on a page, but allowing yourself to go to N+1. If the paragraph is exactly 3 lines long, then a page length of N+2 can eliminate both the widow and orphan. 
 + 
 +If you must limit the page size to a maximum of N lines, then you can use a page length of N-1 lines to force another line onto the top of the next page. If headings occur prior to the orphan, then they must be moved to the next page as well. Paragraphs exactly 3 lines long that have been split in either direction would just be moved to the next page, along with any headings. 
 + 
 +===== PDF requirements ===== 
 + 
 +  * 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 will be sized for ??? 
 + 
 + 
 + 
 +We have talked about using [[http://www.princexml.com|PrinceXML]] to generate PDF. 
  
 ===== EPUB ===== ===== EPUB =====
design/formats.txt · Last modified: 2013/10/15 19:07 by rsewikiadmin

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki