Convert TEXTILE to TEXINFO
Turn TEXTILE files into TEXINFO. A Texinfo manual with lists, tables, links and footnotes; each top-level heading becomes a chapter with its own node and menu entry.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop TEXTILE files on the dialor turn it to pick what to do
A Texinfo manual from Textile markup.Each top-level heading becomes a chapter with its own node.
What you get
One Texinfo file that holds a manual. Each top-level heading becomes a chapter with its own node and its own menu entry, so the manual has a menu that leads to every chapter.
Lists, tables, links and footnotes carry over into the Texinfo file.
What changes
Every line break inside a paragraph is kept, as Textile does. A line you break by hand in the Textile file stays a break in the Texinfo file.
Cell spans in tables are not kept. Images stay as links and are not embedded in the output.
Where to go next
For other formats built from the same source, see every TEXTILE conversion. To see what else produces Texinfo, see every TEXINFO conversion.
TEXTILE and TEXINFO.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
Texinfo
Texinfo, the source of GNU manuals that becomes Info pages, HTML and printed books.
- Extensions
- .texi .texinfo
- MIME type
- application
/x -texinfo - Kind
- Text and data
In your code.The same TEXTILE to TEXINFO conversion through the API, for your app or your agent.
$ cv convert report.textile report.texi$ cv convert report.textile report.texiQuestions.What people ask about TEXTILE to TEXINFO.
Each top-level heading becomes a chapter with its own node and menu entry.
Yes. Every line break inside a paragraph is kept, as Textile does.
No. Cell spans are not kept.
Images stay as links. They are not embedded in the Texinfo file.