From ed8076801c73d0df32d10561ce567faeb73e958a Mon Sep 17 00:00:00 2001 From: Jonas Jenwald Date: Sat, 29 Oct 2022 20:29:55 +0200 Subject: [PATCH] The SVG back-end has now been deprecated in three releases --- Frequently-Asked-Questions.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/Frequently-Asked-Questions.md b/Frequently-Asked-Questions.md index 3f2ca5b..2daa70e 100644 --- a/Frequently-Asked-Questions.md +++ b/Frequently-Asked-Questions.md @@ -14,7 +14,6 @@ * [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 the 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) @@ -209,11 +208,6 @@ 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. - -## 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 both slower and uses more memory than the canvas back-end. - ## PDF.js is fetching the entire PDF file from a server. Can it fetch only the required portions for rendering?