You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PDF support is an important part of the Readium Mobile toolkit and something that we also want to replicate on the Web.
In Readium Mobile, this support is based on native support for PDF (PDFKit on iOS, iPadOS and macOS while Android uses PDFium) as well as PSPDFKit (only on Android for now and which requires a commercial license).
On the Web, there's no native support for PDF, which means that using a PDF library will be mandatory. Rather than re-inventing the wheel, Readium Web will integrate an existing project (such as PDF.js) and make sure that the navigator and all of its usual API (Preferences or Content Iterator API for example) behave as expected and consistently with the rest of the project.
This integration must support the ability to stream a PDF using byte ranges as long as the PDF is linearized in order to provide a decent UX for larger PDF files.
The text was updated successfully, but these errors were encountered:
I've created this issue in the Web repo but most of the work should be handled in the ts-toolkit.
There are very few reasons why a PDF should be parsed and streamed from the go-toolkit, aside from potentially encrypting/decrypting byte ranges on the fly.
PDF support is an important part of the Readium Mobile toolkit and something that we also want to replicate on the Web.
In Readium Mobile, this support is based on native support for PDF (PDFKit on iOS, iPadOS and macOS while Android uses PDFium) as well as PSPDFKit (only on Android for now and which requires a commercial license).
On the Web, there's no native support for PDF, which means that using a PDF library will be mandatory. Rather than re-inventing the wheel, Readium Web will integrate an existing project (such as PDF.js) and make sure that the navigator and all of its usual API (Preferences or Content Iterator API for example) behave as expected and consistently with the rest of the project.
This integration must support the ability to stream a PDF using byte ranges as long as the PDF is linearized in order to provide a decent UX for larger PDF files.
The text was updated successfully, but these errors were encountered: