If I'm not claiming the root, I'd probably stick with EBook::Tools (and EBook::Tools::Unpack, etc.), since the module doesn't require strict adherence to IDPF specs (there's even special code for handling Mobipocket extensions, for instance) — it only requires that the e-book format be convertible to a superset of one of the IDPF specs internally, and that covers a pretty wide range. EPub books are just IDPF OPF zipped up, Mobipocket is a superset of IDPF OEB 1.2, and Microsoft Lit is pretty much exactly IDPF OEB 1.2 wrapped in a proprietary container. I think the only popular container formats not based on IDPF spec are E-Reader and iSilo (and maybe Plucker for the PalmOS-only crowd), but I should eventually be able to handle imports and exports to iSilo's container format as well (since it is XML), and Plucker is just a HTML parsing toolchain that I can plug in pretty easily at least for generation. Since Mobipocket's PRC is also based on PalmDB, I may even get it to go both ways eventually.

It would seem a little odd to me down the line to pick up EBook::IDPF to use an iSiloX ixl file to create a Mobipocket prc, for instance, changing the author name along the way, and I do foresee that kind of functionality.

Update: Also, there is a synopsis of sorts, except that it's called 'Example' down at the bottom, and for some reason pod2html didn't link to it properly. I'll switch it up to Synopsis at the top before release.

In reply to Re^2: RFC: claiming the CPAN root namespace 'EBook' by AZed
in thread RFC: claiming the CPAN root namespace 'EBook' by AZed

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.