Convert VIMWIKI to TEXINFO
Turn VIMWIKI 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 VIMWIKI files on the dialor turn it to pick what to do
A Texinfo manual from your wiki pages.Lists, tables, links and footnotes come across as Texinfo source.
What you get
One Texinfo file that reads as a manual. Each top-level heading becomes a chapter with its own node and its own menu entry, so the manual has a menu to move through.
Lists, tables, links and footnotes are kept as Texinfo versions of themselves. The result is source that Texinfo can turn into Info pages, HTML or a printed book.
What changes
Check boxes lose their ticks. An item stays in its list, but whether it was checked or not is not carried over.
Wiki links point to page names. Images stay as links and are not embedded in the manual.
VIMWIKI and TEXINFO.What each format is.
The formats
Vimwiki
Vimwiki pages, the personal wiki and diary kept inside the Vim editor.
- Extensions
- .vimwiki
- MIME type
- text
/x -vimwiki - 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 VIMWIKI to TEXINFO conversion through the API, for your app or your agent.
$ cv convert report.vimwiki report.texi$ cv convert report.vimwiki report.texiQuestions.What people ask about VIMWIKI to TEXINFO.
Each top-level heading becomes a chapter. It gets its own node and its own menu entry.
The items stay in their lists, but the ticks are lost. A checked box and an empty one look the same.
No. Images stay as links to the picture, and the picture itself is not placed in the file.
You get one file. All the chapters are in the same Texinfo source.