Convert POD to MUSE

Turn POD files into MUSE. An Emacs Muse document with headings, lists, tables, links and footnotes.

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 POD turned into a Muse document.Headings, lists, tables, links and footnotes carry over into one MUSE file.

  1. What you get

    An Emacs Muse document built from your POD file. Headings, lists, tables, links and footnotes come across as Muse markup.

    The result is a single file. It uses the markup that Emacs Muse and Amusewiki read.

  2. What changes or is dropped

    Verbatim paragraphs become code. Links to other manual pages keep only the name of the page.

    Paragraphs marked with =for comment are dropped. Blocks opened with =begin for HTML pass through only where HTML can be kept.

  3. Related conversions

    For other formats, see every POD conversion. To see where MUSE files can go, see every MUSE conversion.

POD and MUSE.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 · MUSE

Muse

Emacs Muse and Amusewiki markup, used for books and essays in online libraries.

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

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

terminal
$ cv convert report.pod report.muse
$ cv convert report.pod report.muse

Questions.What people ask about POD to MUSE.

01OF 04

Yes. Headings and lists are kept in the Muse document, along with tables, links and footnotes.

Verbatim paragraphs in the POD become code in the Muse file.

They keep only the name of the page.

No. Paragraphs marked with =for comment are dropped.

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