|
|
Rank: Member
Groups: Member
Joined: 6/7/2017
Posts: 13
|
Hi,
Is there anything we can do to avoid "ProcSets" in the generated PDF when converting HTML to PDF (and using PDF_A standard)?
We have to deliver the PDF files to a third party, whose validator does not accept ProcSets as a valid part of the PDF/A 2b standard (that they're using, I'm aware we can only generate PDF/A 1a but I think that should be ok as a subset of 2b)
Thanks a lot in advance!
(using html to pdf version 19.1.95)
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,217
|
Unfortunately there is no way to avoid ProcSets. There have been a number of PDF/A specifications that were published over the years. However we only support PDF/A 1a. Others are not supported due to a number of reasons. One of the main reason is those specifications are relatively outdated giving today's hardware capabilities. For example, one of the main restrictions with PDF/A1 is transparency and it is hard to imagine any imaging device today can not handle transparency. The other reason one of the main source of the PDF files generated through our library is HTML using our HTML to PDF converter, many features will not work correctly if restrictions on PDF/A were applied. As such we do not have any plans to support other standards at this time. Sorry about it!
|
|
Rank: Member
Groups: Member
Joined: 6/7/2017
Posts: 13
|
Thank you for the quick response!
If others find this question, a workaround that can be applied is to use a component that allows you to convert pdfs to pdf/a X after rendering, for us that might end up being the solution.
|
|