Live data from Hacker News

Ask HN: Is PDF generation a real pain for developers?

news.ycombinator.com

11–20 of 31 posts

Re: Ask HN: Is PDF generation a real pain for developers?

#11
Its a terribly painful. I have tried every single one of the options. I am still finding it extremely difficult to get it working. Once I managed to get it to print to pdf, then started the bigger problem 'Paging'.

Paging is quite painful. I am writing my own code to split tables to fit into pages.

If you can solve this problem. I would gladly pay.

Re: Ask HN: Is PDF generation a real pain for developers?

#12

It is tedious to code the layout and design of the PDF using code libraries such as FPDF, Prawn etc. I recently used Prince[1] to generate a PDF version of a web-based book. The PDF needed to be suitable for professional printing (crop marks, bleed, trim, etc.). Prince was the only solution I could find that came even close to being adequate for the job, and it exceeded my expectations. Creating the HTML for Prince w…

PrinceXML doesn't support a lot of the Html5 and CSS3. Canvas support doesnt exist, so I cant print charts.

Re: Ask HN: Is PDF generation a real pain for developers?

#13
post #5

The target market that will pay for PDF generation is probably not developers. A competent developer can generate PDF's with the mentioned libraries rather quickly. We deal with a lot of PDF generation where I work, and it is not something that enters our minds to outsource because it's pretty fast and easy to do. For us, the generated PDF's do not need great design or layout, they just need the info in a printable f…

I disagree, If we are dealing with simple invoices and stuff. Once you start dealing with reports containing charts, it all goes haywire

Re: Ask HN: Is PDF generation a real pain for developers?

#15
It is tedious to layout a PDF but actual pain points are handling variable sized images and amounts of text, try formatting recipes to a PDF... Your demo video explains the features but not how it can solve anything that is a major problem to me.

The concept here in designing a template to be filled later is a brilliant idea, but I think its the delivery of the product that may pose the biggest problem. PDF generation doesn't have the same level of complexity as video encoding or payments so when it is used, its expected to just work as the environment doesn't change.

This introduces what I think is the main issue, if I build a website for a client, as a developer I never want to see it come back with problems, so its not worth introducing the risk of a third party service for the sake of a few hours of tedious work. At the other end of the industry any company producing a webapp may have problems with this simply due to how fundamental the feature can be, PDF generation doesn't require the same infrastructure as video encoding or payments, so they will have very different tradeoffs. Your main problem here is that you have no competition so I have nowhere to go if you close and the design online feature is essentially a vendor lockin.

Your assumptions are right but they are what a developer wants, the decisions are mostly made by management where future risk is more important than short term convenience.

Personally I think this product in particular would be much more suited to being a standalone package.

Re: Ask HN: Is PDF generation a real pain for developers?

#17

Its a terribly painful. I have tried every single one of the options. I am still finding it extremely difficult to get it working. Once I managed to get it to print to pdf, then started the bigger problem 'Paging'. Paging is quite painful. I am writing my own code to split tables to fit into pages. If you can solve this problem. I would gladly pay.

We are looking into dynamic layout where tables can be split. It would be great to work along side you. Can I have your contact?

Re: Ask HN: Is PDF generation a real pain for developers?

#18

Browsers let you print a page as PDF. Which use-cases does Pagify solve?

It does print the web page. But when it comes to print-friendly reports and quotes you need some library or print ready web page. So we allow developers to create a template that is print ready. And then using an API call they can merge data and generate PDF.

Re: Ask HN: Is PDF generation a real pain for developers?

#19

I work in the DOCCM (Document Output for Customer Communications Management) space, which in a certain light is just generating PDFs (well, perhaps a bit more complex than that...). Enterprise deals in this space will have 6 or 7 zeros, so yes, there is a market for generating PDFs. There are already some cloud providers out there (like exari - it's been a while but I remember their stuff being pretty cool.) That's a…

Thanks for the feedback. We are going after the SF market, but there is already competition. As far as pricing model is concerned we would do that on the no of pages one generates. Do you think developers are not the right market? Can we offer it to developers in some form?

Re: Ask HN: Is PDF generation a real pain for developers?

#20
post #15

It is tedious to layout a PDF but actual pain points are handling variable sized images and amounts of text, try formatting recipes to a PDF... Your demo video explains the features but not how it can solve anything that is a major problem to me. The concept here in designing a template to be filled later is a brilliant idea, but I think its the delivery of the product that may pose the biggest problem. PDF generatio…

Thanks. Do you think by using an HTML template that can be filled in later is a better idea than visual designer?
Post reply on HN