Convert RST to CHUNKEDHTML
Turn RST files into CHUNKEDHTML. Linked HTML pages in a zip, a contents page and one page for each top-level heading, with headings, lists, tables, links, footnotes and math.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop RST files on the dialor turn it to pick what to do
A zipped website from your RST file.One contents page and one linked page per top-level heading.
What you get
A single zip file of linked HTML pages. It holds a contents page and one page for each top-level heading in your RST file, so a document with several chapters becomes several pages.
Headings, lists, tables, links, footnotes and math are carried over. The zip can go on any web server as it is.
What changes or is dropped
Directives that only Sphinx knows, such as toctree, keep just their text. They do not do what they do in a Sphinx build, so a toctree does not build a contents tree from your files.
Comments are dropped and do not appear in the pages. Images stay as links and are not placed inside the zip.
RST and CHUNKEDHTML.What each format is.
The formats
reStructuredText
reStructuredText, the markup of Python documentation and Sphinx.
- Extensions
- .rst
- MIME type
- text
/x -rst - Kind
- Text and data
Chunked HTML
A document split into linked HTML pages, one per chapter, with a contents page, zipped to put on any web server.
- Extensions
- .html.zip
- MIME type
- application
/x -chunked -html +zip - Kind
- Text and data
In your code.The same RST to CHUNKEDHTML conversion through the API, for your app or your agent.
$ cv convert report.rst report.html.zip$ cv convert report.rst report.html.zipQuestions.What people ask about RST to CHUNKEDHTML.
Each top-level heading starts its own page. A contents page links the pages together.
Only as text. Directives that only Sphinx knows, such as toctree, keep their text and nothing more.
No. Comments are dropped from the output.
No. Images stay as links to where they point. For more routes from this format, see every RST conversion.