I've recently noticed that the embedded PDF renderers in Chrome and Firefox will sometimes draw the downloaded pdf file as 'n' empty pages, and other times there will be no problem at all. Firefox reports a 'flate' error in the console when this happens. If you download/save an empty rendered file, then open it with another viewer it will render correctly. The contents that we feed to Prince to generate the PDF are static.
Note that there is another, less frequent failure case that we've seen where the document contains badly rendered text, as though it had defaulted to ascii.
I've experimented a little with the settings here and if I set '--pdf-profile=PDF/A-1b', as opposed to having no pdf profile set, the resulting pdf files are a lot more consistent when checked with a binary diff.
If you could shed any light on this issue or provide any guidance it would be much appreciated.
Note that there is another, less frequent failure case that we've seen where the document contains badly rendered text, as though it had defaulted to ascii.
I've experimented a little with the settings here and if I set '--pdf-profile=PDF/A-1b', as opposed to having no pdf profile set, the resulting pdf files are a lot more consistent when checked with a binary diff.
If you could shed any light on this issue or provide any guidance it would be much appreciated.