Go to file
Tim van der Meij c7af2db2ec
Implement unit tests for the encodings and fix missing items
Initially I just implemented the unit tests, but quickly found that they
were failing my expectation of having a size of 256 items. Some of them
did contain 256 items and some did not. I looked up various resources
and figured that they indeed all need to have 256 items. One of the good
resources is https://github.com/davidben/poppler/blob/master/poppler/FontEncodingTables.cc

Aside from some missing `notdef` (empty string) entries at the end of
the arrays, which I assume causes issues since it may cause
out-of-bounds array access which in JavaScript gives `undefined`, there
was a `notdef` entry missing in the `MacExpertEncoding`, causing the
entries after that to be shifted. This fix for this is similar to the
one in #8589.

The unit tests verify that, for known encoding names, the return value
is not only an array, but that it is also of the right length and
contains only strings.
2017-12-24 18:14:40 +01:00
.github Attempt to clarify the meaning of "extension" in the ISSUE_TEMPLATE 2017-10-21 11:32:03 +02:00
docs Update index.md 2017-11-30 09:50:00 +09:00
examples Add btoa back to domstubs.js 2017-11-28 16:34:53 +08:00
extensions Switch to using mozilla/recommended configuration for extensions/firefox. 2017-12-08 18:58:48 +00:00
external Remove __pdfjsdev_webpack__, use webpack options 2017-07-09 16:35:48 +02:00
l10n Update l10n files 2017-11-30 13:35:00 +01:00
src Implement unit tests for the encodings and fix missing items 2017-12-24 18:14:40 +01:00
test Implement unit tests for the encodings and fix missing items 2017-12-24 18:14:40 +01:00
web Improve visibility of the findInput placeholder in Chrome 2017-12-12 15:34:51 +05:30
.editorconfig Uses editorconfig to maintain consistent coding styles 2015-11-14 07:32:18 +05:30
.eslintignore Adds streams-lib polyfill and exports ReadableStream from shared/util. 2017-05-20 00:26:34 +05:30
.eslintrc Enable the no-var ESLint rule in the /web folder 2017-11-05 16:53:47 +01:00
.gitattributes Fixing C++,PHP and Pascal presence in the repo 2015-10-29 13:03:51 -05:00
.gitignore Update all packages to the most recent version 2017-09-30 16:26:24 +02:00
.gitmodules Update fonttools location and version (issue 6223) 2015-07-17 12:51:09 +02:00
.mailmap Add mgol's name to AUTHORS, add .mailmap 2017-11-22 10:46:11 +01:00
.travis.yml Travis CI: use most recent version of NPM 2016-10-27 21:10:19 +02:00
AUTHORS Add SehyunPark to AUTHORS 2017-11-29 22:24:08 +09:00
EXPORT Adds ECCN response statement 2017-10-23 13:31:36 -05:00
gulpfile.js 'worker-loader' requires 'webpack' as peerDependency 2017-12-07 23:10:12 +01:00
LICENSE cleaned whitespace 2015-02-17 11:07:37 -05:00
package.json Update eslint-plugin-mozilla, and enable mozilla/use-services rule. 2017-11-24 16:58:36 +00:00
pdfjs.config Version 2.0 2017-10-30 08:18:25 -05:00
README.md Update README.md 2017-11-18 21:29:20 +09:00
systemjs.config.js Update all packages to the most recent version 2017-09-30 16:26:24 +02:00

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:

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.

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 to Tools > Extension and load the (unpackaged) extension from the directory build/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:

Please keep in mind that this requires an ES6 compatible browser; refer to Building PDF.js for usage with older browsers.

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.

Including via a CDN

PDF.js is hosted on several free CDNs:

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 in 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 (Internet Relay Chat):

  • #pdfjs on irc.mozilla.org

File an issue:

Follow us on twitter: @pdfjs