Sakurai/pdf.js
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
9,053 Commits 1 Branch 80 Tags 254 MiB
JavaScript 79.4%
Fluent 18.3%
CSS 1.5%
HTML 0.8%
ae2cc9119b
Go to file
Jonas Jenwald ae2cc9119b Add a couple more, mostly text, reference tests for non-embedded symbolic fonts without included encoding information 
I've started to look into how we can fix issue 7580, but quickly became worried that fixing it could easily mean that we'd trade one fixed PDF file for a multitude of broken ones.

Hence I started going through the history of the code that choose the fallback encoding, and noticed that it has been changed a number of times over the years to deal with various cases of weirdness/errors in non-embedded fonts.
To my relief it turned out that almost all the PRs, please see a possibly incomplete [list here], that changed this code actually included `eq` test-cases.

However, in one case it appears that a PR missed to add a test-case. Furthermore since the fallback encoding may also be the only source for creating a `toUnicode` map, changing the encoding could possibly regress only the text-selection despite a PDF file still rendering correctly.
Therefore, this PR adds one new `eq` test, and also a number of additional `text` tests for PDF files already present in the test-suite.

Note that it's obviously possible that there's a certain overlap between the added tests, but I'd be *a whole lot* more concerned with causing regressions.
2016-09-11 16:38:39 +02:00
.github Add an ISSUE_TEMPLATE 2016-03-23 22:48:14 +01:00
docs Github -> GitHub 2016-05-26 11:11:50 -07:00
examples [mobile-viewer] Add an async close method to the example, and change open to also be async (issue 7571) 2016-08-27 12:57:34 +02:00
extensions Add a enhanceTextSelection preference 2016-09-08 10:22:01 +02:00
external Unbreak the importl10n command by updating the links to point to hg.mozilla.org instead of mxr 2016-06-22 09:41:11 +02:00
l10n Update translations 2016-08-28 16:14:03 +02:00
src Don't duplicate the first entry in the charCodeToGlyphId map for CIDFontType2 fonts with a CIDToGIDMap that already mapped the first entry to a non-zero glyphId (issue 7544) 2016-09-09 22:33:41 +02:00
test Add a couple more, mostly text, reference tests for non-embedded symbolic fonts without included encoding information 2016-09-11 16:38:39 +02:00
web Merge pull request #7609 from Snuffleupagus/enhanceTextSelection-pref-hack 2016-09-09 16:38:45 +02:00
.editorconfig Uses editorconfig to maintain consistent coding styles 2015-11-14 07:32:18 +05:30
.gitattributes Fixing C++,PHP and Pascal presence in the repo 2015-10-29 13:03:51 -05:00
.gitignore Added svg export tool 2014-08-14 23:18:19 +05:30
.gitmodules Update fonttools location and version (issue 6223) 2015-07-17 12:51:09 +02:00
.jshintignore Remove mozcentral test files. 2015-11-11 15:54:17 -06:00
.jshintrc Adds UMD headers to core, display and shared files. 2015-12-15 13:24:39 -06:00
.travis.yml Use the latest stable Node.js version on Travis CI and enable caching 2016-07-25 15:17:30 +02:00
AUTHORS Adding to authors 2015-11-06 18:52:27 -07:00
gulpfile.js Add opt-out telemetry to the Chrome extension 2016-06-03 20:36:57 +02:00
LICENSE cleaned whitespace 2015-02-17 11:07:37 -05:00
make.js Stop building the AMO extension 2016-08-03 14:44:18 +02:00
package.json Port the publish target to Gulp 2016-04-27 12:54:57 +02:00
pdfjs.config Release of 1.5.188 2016-04-21 15:11:26 -05:00
README.md Update README.md to only guarantee Firefox addon compatibility with the current ESR version 2016-06-25 08:59:59 +02:00

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 checkout:

For further questions or guidance feel free to stop by #pdfjs on irc.mozilla.org.

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

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 productions scripts and build the generic viewer, issue:

$ 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. If you want to support more browsers than Firefox you'll also need to include compatibility.js from build/generic/web/. 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 through the live demos below:

The repo contains a hello world example that you can run locally:

For an introduction to the PDF.js code, check out the presentation by our contributor Julian Viereck:

You can read more about PDF.js here:

Even 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

Join our mailing list:

Subscribe either using lists.mozilla.org or Google Groups:

Follow us on twitter: @pdfjs

Weekly Public Meetings