Show HN: Docverter: convert plaintext to PDF, Docx, or ePub. Now in open beta.
docverter.com
docverter.com
In fact, my observation is that the API documentation was merely copy-pasted from the original. Example:
Pandoc docs[1]: http://dl.dropbox.com/u/144454/hn/from.png
Docverter API[2]: http://dl.dropbox.com/u/144454/hn/to.png
[1] http://johnmacfarlane.net/pandoc/README.html#header-identifi...
[2] http://www.docverter.com/api.html#toc_425
However the author went the extra mile to rename sections thus making it sound like the Markdown extensions are in fact Docverter's.
Sorry to be so negative, but this almost seems like acting in bad faith and selling a GPL-licensed software as service under a new name.
One example being: if I was building a new product and wanted to add some reporting/exporting features, I would much rather use a service like this. Document conversion is just infrastructure for those features, and so any time I spend setting up my own system for that is potentially wasted time until I can prove that the features are a success.
Pandoc's an awesome conversion tool, but because of its many supported output formats, some are more reliable than others. For example, it can actually output an HTML/JS-based slide deck - using any of four different JS slideshow libraries - but in my experience only one of them is actually usable, and it's not clear how to customise/style the output.
Of course fixing that as a developer is a simple matter of reading docs / code, but if this product is aiming to be "Pandoc for non-developers", that would be an interesting angle.
You'd generally pay for a service like this if you're running on Heroku or another PaaS and don't want to have to deal with getting Pandoc and various other supporting tools up and running.
"This is a copy of the Pandoc README file, modified to suit Docverter's manifest format."
I'm confused though. In another comment [1] zrail says this (the HTML-to-PDF in particular) is built on a Java library. Is Flying Saucer based on Pandoc? Do you use one sometimes and the other other times?
The point is that you don't have to worry about those pieces, though, since Docverter abstracts over them with a simple API.
You could also do something more fully-featured, like a sandbox where you can upload your own files. Perhaps it could be an "evaluation plan" which has a maximum of 10 conversions per month. (Then again, $5 isn't really that much to pay to evaluate a service.) Or maybe unlimited conversions with the evaluation plan, but the output files have a watermark?
I had no idea this was based on pandoc until I read the HN comments. So, cool!
My quick "dumb" question -- what's the pitch for using this vs. what I would call more traditional conversion tools? My project will need some HTML -> PDF goodness and I was planning on researching and running some sort of local / server-side package (which I presume exists, though I haven't researched them yet).
Either way, congrats on the launch - this makes a lot of sense and sounds like a great utility.
Flying Saucer excels against the alternatives I looked at in a few ways. First, Pandoc's built in PDF writer uses a LaTeX intermediary which doesn't support anything that web writers have come to expect. Second, the other tools were webkit based which variously didn't support the page media spec, didn't support embedding fonts, or both. Others were custom one off of desktop tools that wouldn't work how I need for Docverter.
I posted last week about Docverter, my plain text to rich text conversion tool. It's actually ready for people to start using now. I'll be here all day to answer questions.
Edit to add: I added docverter PDF conversions to my blog last night and it took all of an hour. Check out the Download PDF link toward the bottom here: http://bugsplat.info/2012-08-11-task-oriented-dotfiles.html
Code is here: https://github.com/peterkeen/bugsplat.rb/blob/master/app.rb#...
Here's a few projects to look at, if you haven't already:
1. http://www.docx4java.org/trac/docx4j 2. https://github.com/mikemaccana/python-docx There are some interesting forks and more active forks, but this is the original python-docx
Having never looked at it myself I'm not really sure why it would be so painful. Are the formats just super wacky?
Maybe T&C can protect you in this scenario but maybe not.
Recently I designed some flexible forms meant for printing, but I used php/html/css to generate it. I discovered that it's really hard to get a good quality print out of a webpage. If you use screenshots you get poor resolutions, and direct to print/pdf conversion tools didn't render the CSS all that well.
Don't see how T&C couldn't cover such scenarios in which the user has explicit permission to generate a copy of a webpage.
I'm building software where the output must be in docx, wondering how far I can go in not having to deal with word automation to get the output I want into a Word Doc.
I know it isn't easy to set up the pricings but would there be any "pay per use" for people like me?