In the PDF from issue 8527, the clip operator (W) shows up before a path is defined. The current SVG backend however expects a path to exist before generating a `<svg:clipPath>` element. In the example, the path was defined after the clip, followed by a endPath operator (n). So this commit fixes the bug by moving the path generation logic from clip to endPath. Our canvas backend appears to use similar logic: `CanvasGraphics_endPath` calls `consumePath`, which in turn draws the clip and resets the `pendingClip` state. The canvas backend calls `consumePath` from multiple other places, so we probably need to check whether doing so is also necessary for the SVG backend. I scanned our corpus of PDF files in test/pdfs, and found that in every instance (except for one), the "W" PDF operator (clip) is immediately followed by "n" (endPath). The new test from this commit (clippath.pdf) starts with "W", followed by a path definition and then "n". # Commands used to find some of the clipping commands: grep -ra '^W$' -C7 | less -S grep -ra '^W ' -C7 | less -S grep -ra ' W$' -C7 | less -S test/pdfs/issue6413.pdf is the only file where "W" (a tline 55) is not followed by "n". In fact, the "W" is the last operation of a series of XObject painting operations, and removing it does not have any effect on the rendered PDF (confirmed by looking at the output of PDF.js's canvas backend, and ImageMagick's convert command). |
8 years ago | |
---|---|---|
.github | Change the `importl10n` script to use the Nightly channel | 8 years ago |
docs | Replace a couple of leftover `make.js` references with `gulpfile.js` in docs/comments | 8 years ago |
examples | Adds gulp dist-install command; using pdfjs-dist package in examples. | 8 years ago |
extensions | Bug 1353029 - Pass PdfJs.enabled into child on change. | 8 years ago |
external | Added sendWithStream method in MessageHandler. | 8 years ago |
l10n | Update l10n files | 8 years ago |
src | Move svg:clipPath generation from clip to endPath | 8 years ago |
test | Move svg:clipPath generation from clip to endPath | 8 years ago |
web | Merge pull request #8535 from Snuffleupagus/app-close-pageRotation-downloadComplete | 8 years ago |
.editorconfig | Uses editorconfig to maintain consistent coding styles | 10 years ago |
.eslintignore | Adds streams-lib polyfill and exports ReadableStream from shared/util. | 8 years ago |
.eslintrc | Fix the remaining cases of inconsistent spacing and trailing commas in objects, and enable the `comma-dangle` and `object-curly-spacing` ESLint rules | 8 years ago |
.gitattributes | Fixing C++,PHP and Pascal presence in the repo | 10 years ago |
.gitignore | Example for converting PDF to PNG using the Node canvas library | 8 years ago |
.gitmodules | Update fonttools location and version (issue 6223) | 10 years ago |
.travis.yml | Travis CI: use most recent version of NPM | 9 years ago |
AUTHORS | Adding to authors | 10 years ago |
LICENSE | cleaned whitespace | 10 years ago |
README.md | Adds gulp dist-install command; using pdfjs-dist package in examples. | 8 years ago |
gulpfile.js | Adds gulp dist-install command; using pdfjs-dist package in examples. | 8 years ago |
package.json | Merge pull request #8366 from yurydelendik/rm-shelljs | 8 years ago |
pdfjs.config | Fixes stable version number | 8 years ago |
systemjs.config.js | Fix the remaining cases of inconsistent spacing and trailing commas in objects, and enable the `comma-dangle` and `object-curly-spacing` ESLint rules | 8 years ago |
README.md
PDF.js
PDF.js is a Portable Document Format (PDF) viewer that is built with HTML5.
PDF.js is community-driven and supported by Mozilla Labs. Our goal is to create a general-purpose, web standards-based platform for parsing and rendering PDFs.
Contributing
PDF.js is an open source project and always looking for more contributors. To get involved, visit:
- Issue Reporting Guide
- Code Contribution Guide
- Frequently Asked Questions
- Good Beginner Bugs
- Projects
Feel free to stop by #pdfjs on irc.mozilla.org for questions or guidance.
Getting Started
Online demo
Browser Extensions
Firefox (and Seamonkey)
PDF.js is built into version 19+ of Firefox, however one extension is still available:
-
Development Version - This extension is mainly intended for developers/testers, and it is updated every time new code is merged into the PDF.js codebase. It should be quite stable, but might break from time to time.
-
Please note that the extension is not guaranteed to be compatible with Firefox versions that are older than the current ESR version, see the Release Calendar.
-
The extension should also work in Seamonkey, provided that it is based on a Firefox version as above (see Which version of Firefox does SeaMonkey 2.x correspond with?), but we do not guarantee compatibility.
-
Chrome
- The official extension for Chrome can be installed from the Chrome Web Store. This extension is maintained by @Rob--W.
- Build Your Own - Get the code as explained below and issue
gulp chromium
. Then open Chrome, go toTools > Extension
and load the (unpackaged) extension from the directorybuild/chromium
.
Getting the Code
To get a local copy of the current code, clone it using git:
$ git clone git://github.com/mozilla/pdf.js.git
$ cd pdf.js
Next, install Node.js via the official package or via nvm. You need to install the gulp package globally (see also gulp's getting started):
$ npm install -g gulp-cli
If everything worked out, install all dependencies for PDF.js:
$ npm install
Finally you need to start a local web server as some browsers do not allow opening PDF files using a file:// URL. Run
$ gulp server
and then you can open
It is also possible to view all test PDF files on the right side by opening
Building PDF.js
In order to bundle all src/
files into two production scripts and build the generic
viewer, run:
$ gulp generic
This will generate pdf.js
and pdf.worker.js
in the build/generic/build/
directory.
Both scripts are needed but only pdf.js
needs to be included since pdf.worker.js
will
be loaded by pdf.js
. The PDF.js files are large and should be minified for production.
Using PDF.js in a web application
To use PDF.js in a web application you can choose to use a pre-built version of the library
or to build it from source. We supply pre-built versions for usage with NPM and Bower under
the pdfjs-dist
name. For more information and examples please refer to the
wiki page on this subject.
Learning
You can play with the PDF.js API directly from your browser using the live demos below:
The repository contains a hello world example that you can run locally:
More examples can be found at the examples folder. Some of them are using the pdfjs-dist package, which can be built and installed in this repo directory via gulp dist-install
command.
For an introduction to the PDF.js code, check out the presentation by our contributor Julian Viereck:
More learning resources can be found at:
Questions
Check out our FAQs and get answers to common questions:
Talk to us on IRC:
- #pdfjs on irc.mozilla.org
File an issue:
Follow us on twitter: @pdfjs