Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Linearized PDF #32

Closed
pelinquin opened this issue Sep 12, 2012 · 2 comments
Closed

Linearized PDF #32

pelinquin opened this issue Sep 12, 2012 · 2 comments

Comments

@pelinquin
Copy link

Does jsPDF use the possibility to render linearized PDF; render the first page quickly and concatenate the other pages in background ?. Of course the server is in charge of sending the PDF chunks asynchronously.

@dvdotsenko
Copy link
Collaborator

@pelinquin

I am only one of a few people who contributes to jsPDF, so this applies to only to me:

  1. Linearization as a feature is nowhere near on my (personal/corporate) radar, as it's a "nice to have" feature and is completely overshadowed by other needed functionality, like font-file support, unicode support etc.

2.The types and size of PDF you would produce in the browser is unlikely to benefit much from linearization. Although some of the guys who use jsPDF use it on server, I see absolutely no use for jsPDF on the server, as other much-more-capable PDF toolkits are available now for real server languages/toolkits (.Net, Python, PHP etc). When your PDFs are so large (images, embedded fonts, many many pages etc) that you need linearization, you likely will need non-javascript, serious server-side code with fast access to media, database and no memory constraints. (You could guess here, my focus is on running jsPDF in the browser).

Again. I am just one of the contributors. Yet, based on 1 and 2 above, I see Linearization as "will not implement in foreseeable future" kind of feature for jsPDF.

@pelinquin
Copy link
Author

OK I understand your priorities.
I have to investigate first the requirements on server side and HTTP range call to see it there are side requirements on client side jsPDF code. I will then ask for a more precise question if any.
From a user viewpoint, I think it will be fundamental to have fastweb PDF rendering but I found the PDF linearization process in Adobe spec very complex...I need to learn more on this.
Thanks anyway.

@diegocr diegocr closed this as completed Feb 8, 2014
Uzlopak pushed a commit that referenced this issue Feb 5, 2020
fix unnecessary console warning for preexisting acroform classes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants