Marmelator/pdf.js
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Include a question about the various back-ends we have.

Tim van der Meij 2019-01-24 23:14:03 +01:00
parent ddd218c6ab
commit 4baff9d724
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Frequently-Asked-Questions.md

@ -13,6 +13,7 @@
* [I have a really great idea. Where is the best place to record it?](#idea)
* [I'm developing a custom solution based on PDF.js core library. Can you help me?](#custom)
* [I want to render all 100 pages in a document at a high resolution. Is it a good idea?](#allthepages)
* [There are two back-ends, canvas and SVG. Which one should I use?](#backends)
* [PDF.js is fetching the entire PDF file from a server. Can it fetch only the required portions for rendering?](#range)
* [What is a latest stable version of PDF.js?](#version)
* [What types of PDF files are slow in PDF.js? Can I optimize a PDF file to make PDF.js faster?](#optimize)
@ -187,6 +188,11 @@ Not really. You can count yourself: a letter page size is 816⨉1056px at 96DPI
The demo viewer creates, renders, and holds canvases only for visible pages to reduce the amount of used memory. Our recommendation is to create and render only visible pages.
<a name="backends"></a>
## There are two back-ends, canvas and SVG. Which one should I use?
You should use the default, which is the canvas back-end, since it is stable and supported. The SVG back-end is experimental and is not feature complete. The advantage of the SVG back-end is rendering quality, but the disadvantage is that it's currently slower than the canvas back-end.
<a name="range"></a>
## PDF.js is fetching the entire PDF file from a server. Can it fetch only the required portions for rendering?