You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
owner:henrik@levkowetz.comresolution_fixedtype_defect | by tony@att.com
With the attached input, starting around section 3.1.3, tables are ommitted from the output and the HTML starts getting indented further and further to the right.
Here is part of the output:
<p id="rfc.section.3.1.3.p.1">There is some advantage to having the PDF files look like the text or HTML renderings of the same document. There are several options even so. The PDF </p>
<ol/>
<p> (Note that numbers 1 and 2 are what are currently produced by the RFC Editor on their web site.) </p>
<p id="rfc.section.3.1.3.p.2">Recommendation: the PDF rendition should look like the HTML rendition, at least in spirit. For example, some differences from the HTML rendition might be: </p>
<ul class="empty"/>
Issue migrated from trac:263 at 2022-02-05 12:38:55 +0000
The text was updated successfully, but these errors were encountered:
Merged in 26961cd from Jim Schaad:
Change to emit html not xhtml. Addresses issues #263 and #279.
Also updated additional test masters needed to make the tox
tests pass, and changed the html encoding and decoding to use
utf-8, to work with the unicode and utf-8 tests.
owner:henrik@levkowetz.com
resolution_fixed
type_defect
| by tony@att.comWith the attached input, starting around section 3.1.3, tables are ommitted from the output and the HTML starts getting indented further and further to the right.
Here is part of the output:
Issue migrated from trac:263 at 2022-02-05 12:38:55 +0000
The text was updated successfully, but these errors were encountered: