Convert POD to TEXTILE

Turn POD files into TEXTILE. Textile markup with headings, lists, tables and links.

Converted in an isolated sandbox on our serversDeleted after 24 hours

Drop POD files on the dialor turn it to pick what to do

Perl documentation as Textile markup.Headings, lists, tables and links carry over into one Textile file.

  1. What you get

    A single Textile file made from your POD. Headings, lists, tables and links are written in Textile markup, so the structure of the manual stays in place.

    Verbatim paragraphs, the indented blocks used for code samples, become code in the Textile file.

  2. What changes or is left out

    Links to other manual pages keep only their name. The link target is not carried over.

    Paragraphs marked with =for comment are dropped. Blocks marked with =begin for HTML pass through only where HTML can be kept. Where it cannot be kept, the block is not carried over.

POD and TEXTILE.What each format is.

The formats

From · POD

Perl POD

Plain Old Documentation, the markup of Perl manuals and module docs.

Extensions
.pod
MIME type
text/x-pod
Kind
Text and data
To · TEXTILE

Textile

Textile markup, once common in Rails apps and Redmine.

Extensions
.textile
MIME type
text/x-textile
Kind
Text and data

In your code.The same POD to TEXTILE conversion through the API, for your app or your agent.

terminal
$ cv convert report.pod report.textile
$ cv convert report.pod report.textile

Questions.What people ask about POD to TEXTILE.

01OF 04

Yes. Headings, lists, tables and links are written as Textile markup.

Verbatim paragraphs become code in the Textile file.

No. They are dropped from the output.

Only the name of the page is kept. The link itself is not.

More conversions.Other ways in and out of POD and TEXTILE.