Updating to PDF Version 1.4

[mlgoff59]

How would I go about generating a version 1.4 PDF with this library?

The issue is file size. Currently PDFKit is generating files of about 2mb. Converting them to version 1.4 reduces them to around 800kb.

I know this is similar to the question asked in
https://github.com/devongovett/pdfkit/issues/499#499

but that issue has been closed for a year and a half.

[alafr]

How did you convert it to version 1.4? What happens if you convert the v1.4 file back to version 1.3?
It probably did some compression in addition to the version change.
You can do doc.version = '1.4' but it won't change the file size.

[mlgoff59]

I used Acrobat Pro to convert to v1.4. I have no need to convert back to v1.3

We have another app that generates map sheets and outputs them as v1.4 PDFs. It also outputs SVG files so the user can edit the maps. I'm working on the editor. We need the editor to also output v1.4 PDFs.

Short of opening the file in Acrobat Pro and using the Save As Other I can't do it.

Hence the question, can PDFKit be modified to output a v1.4 file?

[marcelh-gh]

@devongovett @alafr any technical reason for pdfkit being stuck with PDF version 1.3 ?

[mcordoba]

@devongovett any update?

[swftvsn]

All work is waiting #859 to land I think. Maybe @blikblum could give an update where we are atm?

[blikblum]

The PR is ready for merging

[mcordoba]

do you have a scheduled date for the merge?

[blikblum]

it's already merged

[mcordoba]

@blikblum so 0.8.3 has already support for generating pdf 1.4 files? I can't see any info related to this in the commits.

[blikblum]

THey are different things, in the repository the ES6 branch is merged but not yet released. There's yet no work on 1.4 support. Any PR is appreciated

[mcordoba]

But this issue is about 1.4 support. Why are you talking about es6 branch? I guess @swftvsn confused you @blikblum.

I would like to see news about 1.4 support :(

[swftvsn]

All the effort last year was put on ES6 conversion. It would not have made sense back then to code something or anything in coffee script because of the conversion. That's why I pointed out that such effort was underway and not to have high hopes that additional work would be done (such as this issue).

Now that the conversion work is done, one could code the support in ES6 and make a PR. Is it a priority? I'm interested to have the archive formats also. (PDF/A-1, PDF/A-2, PDF/A-3 or PDF/A-4)

[mlgoff59]

swftvsn, makes perfect sense to me. Upgrading to ES6 would have been more important. Upgrading the PDF version support I think should be a high priority. If you could take it to 1.6 that would be even better because of the improved security in 1.6.

[Nonudeveloper]

I am unable to update the pdf version to 1.7.
let pdf = new PDFDocument({
size: 'LEGAL',
pdfVersion: 1.7
});

[liborm85]

duplicate: #332