Convert TEXTILE to DOCBOOK
Turn TEXTILE files into DOCBOOK. A DocBook 5 article with sections, lists, tables, links and footnotes.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop TEXTILE files on the dialor turn it to pick what to do
Textile as a DocBook 5 article.Sections, lists, tables, links and footnotes carry over. Cell spans and images do not.
What you get
One DocBook 5 article built from your Textile text. Sections, lists, tables, links and footnotes are all written into the article.
DocBook is XML for technical books and manuals, and the article is the structured form of the Textile you started with.
Line breaks and images
Every line break inside a paragraph is kept, as Textile treats it. A paragraph written over several lines keeps those lines.
Images stay as links. The picture is not placed in the article.
What it leaves behind
Cell spans are not kept. A table cell that spans several columns or rows in the Textile does not span them in the DocBook table.
To go the other way, use DOCBOOK to TEXTILE.
TEXTILE and DOCBOOK.What each format is.
The formats
Textile
Textile markup, once common in Rails apps and Redmine.
- Extensions
- .textile
- MIME type
- text
/x -textile - Kind
- Text and data
DocBook
DocBook XML, the structured format of technical books and manuals.
- Extensions
- .dbk .docbook
- MIME type
- application
/docbook +xml - Kind
- Text and data
In your code.The same TEXTILE to DOCBOOK conversion through the API, for your app or your agent.
$ cv convert report.textile report.dbk$ cv convert report.textile report.dbkQuestions.What people ask about TEXTILE to DOCBOOK.
One DocBook 5 article. It holds the sections, lists, tables, links and footnotes of the Textile.
Yes. Every line break inside a paragraph is kept, as Textile does.
They stay as links. The images are not placed in the article.
No. Cell spans are not kept, so a cell that spans several columns or rows does not span them in the output.