Does not create PDF or Ebook

Hi @netaction, thanks for the feedback.
So just to clarify: Print My Blog just fetches your posts/pages, puts them onto a single webpage, and does a bit of magic (like adding some CSS and JavaScript) to help them look better when printed. But yes, your web browser is what prints that page. But all browsers (that I know of) can also turn it into a PDF. And using dotEPUB bookmarklet you can also make an eBook.
So Print My Blog doesn’t do the PDF conversion itself, it lets your web browser do that part.
That has PROs and CONs: web browsers can print epically huge printouts (like thousands of posts at once), whereas other plugins that create the PDFs on the server have trouble with more than 100 posts at once. However, it can be a bit confusing, and inconsistent (each browser is different.)
Having said that, all the browsers I’ve tried DO add page numbers to the printouts and PDFs, but not a table of contents, or footnotes.
I am working on integration with a paid service called DocRaptor which will support a table of contents, more control of page numbers (eg Roman numerals gif front matter and regular numbers afterwards), footnotes, and other stuff like page references and using pre-built designs from developers. But it’s still in the works.
Anyways, I hope that explains the situation a little. I did want to clarify that Print My Blog does enable you to print your entire blog, and let visitors print individual posts in a much more printer-friendly format. I think it does a lot more than just tell people to press Control + P.
I’ll be rewriting the plugin description soon and will try to clarify this situation better.
Take care!

Hmmmm so you think this plugin’s name gives an impression that it does the PDF conversion itself, but are disappointed that it hands that part off to the browser.

I think lots of people would agree with you. I hadn’t heard of Pandoc or Apache Fop before, but I don’t think either one of those could be included in the plugin itself (I could setup a server to run them, and do the PDF conversion on the server, but then it would be hard to keep it free). A PHP library like DOM2PDF is an option, or whatever library Anthologize, Kailin’s PDF Creation Station, or MPL Publisher use, is an option too. But in my opinion, browsers do a pretty good enough job of printing. And myself, and quite a few other reviewers, have paid the browser + Print My Blog have often done a superior job than a PDF library + other plugins. So although I’m adding a paid option that will use a 3rd party, paid service for creating more consistent and better PDFs, the free version will continue to use the browser.

So should I rename the plugin? “Archive page generator for data export” is pretty accurate- except that for the past year or so it’s also added print buttons for printing individual posts/pages. I chose to call it “Converter” because that seemed like the term people were most often looking for. I think “Export” implies a machine-readable export, and I think is a bit intimidating for less tech-savvy. So I think your suggestion could be iterated on to make a more accurate description of what the plugin does, but I want to avoid focusing too much on the technical details of what it does, rather than the problem it helps users solve: converting a post, or several posts, into a printout or PDF.

For now, I can’t think of a better thing to call this plugin, but I’m sure I will iterate on it in the future too.

I do think it will be good to try to explain this situation in the plugin’s description though.

In its bulleted list of features, the first one says:

loads all your blog’s posts into a single web page so you can print them from your web browser (to paper, PDF, ePub, or anything your web browser supports)

But I admit that’s a bit far down (under the video) so it’s easy to miss. Would you recommend any other changes to the readme to clarify this plugin doesn’t do the PDF conversion using a library, but instead lets the browser do it? (Keeping in mind we want to setup realistic expectations for what the plugin does, but we also don’t want to bore or confuse the user in technical details.)