PDF Packet Builder
Turn a row into a ready-to-review packet. Map ordinary PDF forms, add measured overlays, and assemble the right documents for each record.
Forms, conditions and a rotated page
A repeatable packet, with a review step
Start here
- Import CSV or edit records. Keep filenames tied to a stable unique ID.
- Add PDFs and inspect their ordinary form fields. Map each field to source values, constants or {{columns}}.
- Add point-based text/checkmark/image overlays where a template has no form.
- Order templates and set simple inclusion conditions.
- Check every record, inspect a filled packet and resolve exceptions.
- Generate the ZIP. It includes one PDF per accepted record, manifest.json and validation.csv. Save the project and original sources.
The synthetic example covers six customers, three templates, form fields, conditional documents and a rotated/cropped dispatch page.
Supported PDFs
Ordinary text fields, checkboxes, fixed single-choice dropdowns and radio groups. Multiline text is supported. Page rotations 0°, 90°, 180° and 270° and CropBoxes inside MediaBoxes are preserved.
Scripts/actions, links/comments, XFA, encryption, signatures, attached files, rich media, Type 3 fonts, unembedded non-standard fonts, JPX/JBIG2 images, non-default UserUnit and unsupported field features are rejected. No encrypted-PDF bypass, arbitrary text editing, signing or sending.
Password/file/rich-text/comb fields, editable or multi-choice dropdowns, export/display option pairs, individually rotated widgets, non-visible fields and orphan widgets are outside this version's scope.
Text & formats
Noto Sans Regular is embedded under the SIL Open Font License. Mapped text supports the font's Latin, Greek and Cyrillic characters and selected punctuation. Complex shaping, combining marks, right-to-left controls, emoji and CJK input are rejected. Choose NFC formatting when it can turn combining text into a supported precomposed form.
Formats: unchanged, trim, uppercase, lowercase, NFC, two decimal places, and explicit ISO/US/UK dates. Date input must be YYYY-MM-DD; ambiguous dates are rejected. No silent font shrinking or overflow clipping.
Checkboxes/checkmarks accept true/false, yes/no or 1/0. A required checkbox must be true. Choice values must match an available option exactly.
Bounds & performance
50 records, 30 data columns, eight PDF templates, eight local images; each PDF at most 5 MiB, eight pages and 80 fields. Sources total 20 MiB. Up to 30 overlays per template. CSV: 1 MiB; project JSON: 4 MiB.
Tested in Chrome 154 on Windows: six-record ZIPs with 18 pages, editable and flattened; 50-record / 200-page preflight. Other browsers and physical printers were not tested. These caps are safeguards, not throughput guarantees.
Each packet: 24 pages / 12 MiB. Batch: 200 pages / 64 MiB ZIP. PDF page sides: 40–1440 points. PDF/image raster objects: up to 4 megapixels. Static local images: 2 MiB and 2048 pixels per edge; animated PNG is rejected.
Parsing/generation runs in an isolated worker with cancellation and a four-minute limit. Preview is bounded to 1200 × 1600 pixels and 30 seconds. Very complex or malformed files can exceed these limits. Divide large batches and use known templates; this is not a general-purpose PDF sanitizer.
Privacy & recovery
Everything needed to run is embedded: code, font, PDF.js workers, standard font data, libraries and documentation. Files stay in this tab's local workflow. No backend, analytics, external fonts or runtime network dependency. CSP blocks outgoing connections; offline tests inspect actual requests.
Projects/recipes save source hashes and mapping descriptors, not PDF/image bytes. Reopen and relink exact originals; renamed files with the same bytes are accepted. No persistent browser storage. Closing/reloading discards unsaved work.
Protected CSV prefixes risky spreadsheet cells with apostrophes. Project JSON preserves exact data. ZIP reports may contain record details and are not encrypted.
Check the result
Unsupported source? Export a plain, unencrypted PDF without actions or unsupported annotations, then reimport and review mappings.
Text does not fit? Shorten the data, reduce the selected point size, or adjust the source field/overlay box. No automatic truncation is applied.
Filename collision? Use a unique ASCII ID or {{__row}}. Paths, reserved device names and unsafe punctuation are rejected.
Paper output? Review every required packet and print at the intended scale. Digital checks do not verify your printer or certify acceptance by another system.
Embedded library & font notices
pdf-lib-LICENSE.txt MIT License Copyright (c) 2019 Andrew Dillon Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. fontkit-LICENSE.txt @pdf-lib/fontkit 1.1.1 Package license: MIT Author: Andrew Dillon <[email protected]> The package distributes its license declaration in README.md (no separate license file): # Purpose of this Fork This project is a fork of https://github.com/foliojs/fontkit created for use in https://github.com/Hopding/pdf-lib. Listed below are changes that have been made in this fork: * Store binary data as compressed base64 JSON so the `fs` module isn't needed to read it back: * [968e35c](https://github.com/Hopding/fontkit/commit/968e35c158589294e9543818f56d0b229b95a475) * [99a35c7](/Hopding/fontkit/commit/99a35c7b0f0f6549d7727bcbc1ddabb7f9ca19bf) * [2f1445d](/Hopding/fontkit/commit/2f1445d9a3f8426bc259690819eea8306a98545a) * [f674bf2-R24](https://github.com/Hopding/fontkit/commit/f674bf2e3c8a8e0a34083e19f0abe65df20520e3#diff-b61f8676a8a37c519e9c3c86c4676208R24), [f674bf2-R13](https://github.com/Hopding/fontkit/commit/f674bf2e3c8a8e0a34083e19f0abe65df20520e3#diff-a73febb5d14ad8d9d7ab6ac378a698aaR13) * Rewrote `Makefile` to `Makefile.js` using `shelljs`: * [a246e7f](https://github.com/Hopding/fontkit/commit/a246e7fda8c0bb5df4be355a993e0ba59f07300e) * Update to Babel 7: * [70049f8](https://github.com/Hopding/fontkit/commit/70049f8f038145cc0caca83c75e0b76f49d11f52) * [8d5b29b](https://github.com/Hopding/fontkit/commit/8d5b29bd00b752a6ab9348e6be1997e201055d31) * Build UMD modules: * [cce995c](https://github.com/Hopding/fontkit/commit/cce995c3378c35b247ed2965e15eb92ffad9ea09) * [08cacef](https://github.com/Hopding/fontkit/commit/08cacefa3e745f83a2c95051e38985b02aa2f16d) * Build ES modules: * [dbe8e9d](https://github.com/Hopding/fontkit/commit/dbe8e9da4e8f2e23f507ba5a767a8109e81fb7ab) * [9363d1f](https://github.com/Hopding/fontkit/commit/9363d1f8e97985d8a94ee6dac1fac39631ee3c77) * Bundle Node dependencies (`stream`, `util`, `Buffer`) into UMD and ES modules so consumers of this lib don't have to deal with them: * [9363d1f](https://github.com/Hopding/fontkit/commit/9363d1f8e97985d8a94ee6dac1fac39631ee3c77) * Accept `Uint8Array` objects for font data instead of `Buffer` objects, so consumers can stick to plain JS regardless of their environment: * [9363d1f-R12](https://github.com/Hopding/fontkit/commit/9363d1f8e97985d8a94ee6dac1fac39631ee3c77#diff-d7e697eff3913f1acaacac8002c3b05eR12) * Add TypeScript declaration file: * [387ebc4](https://github.com/Hopding/fontkit/commit/387ebc418cc04be51d82d39e05f4db01b1bf063f) * [3bafdbc](https://github.com/Hopding/fontkit/commit/3bafdbc3656ebba5251f8d4dc77dcc4b6c11afa6) * [b0241e7](https://github.com/Hopding/fontkit/commit/b0241e7c30cdb83bda6867aa8c9229c1ab1cb8e3) * Remove calls to `new Function()` to allow usage on CSP sites: * [e3dcc8a](https://github.com/Hopding/fontkit/commit/e3dcc8aad014081b8106c47d89049ba9e6f3dd48) * Released to NPM as `@pdf-lib/fontkit` * [873b05d](https://github.com/Hopding/fontkit/commit/873b05d23aecb9f0142fc3ebda593fd2a7d81c17) Also see * https://github.com/Hopding/unicode-properties * https://github.com/Hopding/brotli.js * https://github.com/Hopding/restructure * https://github.com/Hopding/png-ts # fontkit Fontkit is an advanced font engine for Node and the browser, used by [PDFKit](https://github.com/devongovett/pdfkit) and [`pdf-lib`](https://github.com/Hopding/pdf-lib). It supports many font formats, advanced glyph substitution and layout features, glyph path extraction, color emoji glyphs, font subsetting, and more. ## Features * Suports TrueType (.ttf), OpenType (.otf), WOFF, WOFF2, TrueType Collection (.ttc), and Datafork TrueType (.dfont) font files * Supports mapping characters to glyphs, including support for ligatures and other advanced substitutions (see below) * Supports reading glyph metrics and laying out glyphs, including support for kerning and other advanced layout features (see below) * Advanced OpenType features including glyph substitution (GSUB) and positioning (GPOS) * Apple Advanced Typography (AAT) glyph substitution features (morx table) * Support for getting glyph vector paths and converting them to SVG paths, or rendering them to a graphics context * Supports TrueType (glyf) and PostScript (CFF) outlines * Support for color glyphs (e.g. emoji), including Apple’s SBIX table, and Microsoft’s COLR table * Support for AAT variation glyphs, allowing for nearly infinite design control over weight, width, and other axes. * Font subsetting support - create a new font including only the specified glyphs ## Example ```js import fontkit from '@pdf-lib/fontkit'; import fs from 'fs'; // open a font synchronously const fontData = fs.readFileSync('font.ttf'); const font = fontkit.create(fontData); // layout a string, using default shaping features. // returns a GlyphRun, describing glyphs and positions. const run = font.layout('hello world!'); // get an SVG path for a glyph const svg = run.glyphs[0].path.toSVG(); // create a font subset const subset = font.createSubset(); run.glyphs.forEach(function(glyph) { subset.includeGlyph(glyph); }); subset.encodeStream() .pipe(fs.createWriteStream('subset.ttf')); ``` ## Installation ### NPM Module To install the latest stable version: ```bash # With npm npm install --save @pdf-lib/fontkit # With yarn yarn add @pdf-lib/fontkit ``` This assumes you're using [npm](https://www.npmjs.com/) or [yarn](https://yarnpkg.com/lang/en/) as your package manager. ### UMD Module You can also download `@pdf-lib/fontkit` as a UMD module from [unpkg](https://unpkg.com/#/). The UMD builds have been compiled to ES5, so they should work [in any modern browser](https://caniuse.com/#feat=es5). UMD builds are useful if you aren't using a package manager or module bundler. For example, you can use them directly in the `<script>` tag of an HTML page. The following builds are available: * https://unpkg.com/@pdf-lib/fontkit/dist/fontkit.umd.js * https://unpkg.com/@pdf-lib/fontkit/dist/fontkit.umd.min.js When using a UMD build, you will have access to a global `window.fontkit` variable. This variable contains the object exported by `@pdf-lib/fontkit`. For example: ```javascript // NPM module import fontkit from '@pdf-lib/fontkit'; // UMD module var fontkit = window.fontkit; ``` ## API ### `fontkit.create(buffer, postscriptName = null)` Returns a font object for the given buffer. For collection fonts (such as TrueType collection files), you can pass a `postscriptName` to get that font out of the collection instead of a collection object. ## Font objects There are several different types of font objects that are returned by fontkit depending on the font format. They all inherit from the `TTFFont` class and have the same public API, described below. ### Metadata properties The following properties are strings (or null if the font does not contain strings for them) describing the font, as specified by the font creator. * `postscriptName` * `fullName` * `familyName` * `subfamilyName` * `copyright` * `version` ### Metrics The following properties describe the general metrics of the font. See [here](http://www.freetype.org/freetype2/docs/glyphs/glyphs-3.html) for a good overview of how all of these properties relate to one another. * `unitsPerEm` - the size of the font’s internal coordinate grid * `ascent` - the font’s [ascender](http://en.wikipedia.org/wiki/Ascender_(typography)) * `descent` - the font’s [descender](http://en.wikipedia.org/wiki/Descender) * `lineGap` - the amount of space that should be included between lines * `underlinePosition` - the offset from the normal underline position that should be used * `underlineThickness` - the weight of the underline that should be used * `italicAngle` - if this is an italic font, the angle the cursor should be drawn at to match the font design * `capHeight` - the height of capital letters above the baseline. See [here](http://en.wikipedia.org/wiki/Cap_height) for more details. * `xHeight`- the height of lower case letters. See [here](http://en.wikipedia.org/wiki/X-height) for more details. * `bbox` - the font’s bounding box, i.e. the box that encloses all glyphs in the font ### Other properties * `numGlyphs` - the number of glyphs in the font * `characterSet` - an array of all of the unicode code points supported by the font * `availableFeatures` - an array of all [OpenType feature tags](https://www.microsoft.com/typography/otspec/featuretags.htm) (or mapped AAT tags) supported by the font (see below for a description of this) ### Character to glyph mapping Fontkit includes several methods for character to glyph mapping, including support for advanced OpenType and AAT substitutions. #### `font.glyphForCodePoint(codePoint)` Maps a single unicode code point (number) to a Glyph object. Does not perform any advanced substitutions (there is no context to do so). #### `font.hasGlyphForCodePoint(codePoint)` Returns whether there is glyph in the font for the given unicode code point. #### `font.glyphsForString(string)` This method returns an array of Glyph objects for the given string. This is only a one-to-one mapping from characters to glyphs. For most uses, you should use `font.layout` (described below), which provides a much more advanced mapping supporting AAT and OpenType shaping. ### Glyph metrics and layout Fontkit includes several methods for accessing glyph metrics and performing layout, including support for kerning and other advanced OpenType positioning adjustments. #### `font.widthOfGlyph(glyph_id)` Returns the advance width (described above) for a single glyph id. #### `font.layout(string, features = [])` This method returns a `GlyphRun` object, which includes an array of `Glyph`s and `GlyphPosition`s for the given string. `Glyph` objects are described below. `GlyphPosition` objects include 4 properties: `xAdvance`, `yAdvance`, `xOffset`, and `yOffset`. The `features` parameter is an array of [OpenType feature tags](https://www.microsoft.com/typography/otspec/featuretags.htm) to be applied in addition to the default set. If this is an AAT font, the OpenType feature tags are mapped to AAT features. ### Variation fonts Fontkit has support for AAT variation fonts, where glyphs can adjust their shape according to user defined settings along various axes including weight, width, and slant. Font designers specify the minimum, default, and maximum values for each axis they support, and allow the user fine grained control over the rendered text. #### `font.variationAxes` Returns an object describing the available variation axes. Keys are 4 letter axis tags, and values include `name`, `min`, `default`, and `max` properties for the axis. #### `font.namedVariations` The font designer may have picked out some variations that they think look particularly good, for example a light, regular, and bold weight which would traditionally be separate fonts. This property returns an object describing these named variation instances that the designer has specified. Keys are variation names, and values are objects with axis settings. #### `font.getVariation(variation)` Returns a new font object representing this variation, from which you can get glyphs and perform layout as normal. The `variation` parameter can either be a variation settings object or a string variation name. Variation settings objects have axis names as keys, and numbers as values (should be in the range specified by `font.variationAxes`). ### Other methods #### `font.getGlyph(glyph_id, codePoints = [])` Returns a glyph object for the given glyph id. You can pass the array of code points this glyph represents for your use later, and it will be stored in the glyph object. #### `font.createSubset()` Returns a Subset object for this font, described below. ## Font Collection objects For font collection files that contain multiple fonts in a single file, such as TrueType Collection (.ttc) and Datafork TrueType (.dfont) files, a font collection object can be returned by Fontkit. ### `collection.getFont(postscriptName)` Gets a font from the collection by its postscript name. Returns a Font object, described above. ### `collection.fonts` This property is a lazily-loaded array of all of the fonts in the collection. ## Glyph objects Glyph objects represent a glyph in the font. They have various properties for accessing metrics and the actual vector path the glyph represents, and methods for rendering the glyph to a graphics context. You do not create glyph objects directly. They are created by various methods on the font object, described above. There are several subclasses of the base `Glyph` class internally that may be returned depending on the font format, but they all include the following API. ### Properties * `id` - the glyph id in the font * `codePoints` - an array of unicode code points that are represented by this glyph. There can be multiple code points in the case of ligatures and other glyphs that represent multiple visual characters. * `path` - a vector Path object representing the glyph * `bbox` - the glyph’s bounding box, i.e. the rectangle that encloses the glyph outline as tightly as possible. * `cbox` - the glyph’s control box. This is often the same as the bounding box, but is faster to compute. Because of the way bezier curves are defined, some of the control points can be outside of the bounding box. Where `bbox` takes this into account, `cbox` does not. Thus, `cbox` is less accurate, but faster to compute. See [here](http://www.freetype.org/freetype2/docs/glyphs/glyphs-6.html#section-2) for a more detailed description. * `advanceWidth` - the glyph’s advance width. ### `glyph.render(ctx, size)` Renders the glyph to the given graphics context, at the specified font size. ### Color glyphs (e.g. emoji) Fontkit has support for several different color emoji font formats. Currently, these include Apple’s SBIX table (as used by the “Apple Color Emoji” font), and Microsoft’s COLR table (supported by Windows 8.1). [Here](http://blog.symbolset.com/multicolor-fonts) is an overview of the various color font formats out there. #### `glyph.getImageForSize(size)` For SBIX glyphs, which are bitmap based, this returns an object containing some properties about the image, along with the image data itself (usually PNG). #### `glyph.layers` For COLR glyphs, which are vector based, this returns an array of objects representing the glyphs and colors for each layer in render order. ## Path objects Path objects are returned by glyphs and represent the actual vector outlines for each glyph in the font. Paths can be converted to SVG path data strings, or to functions that can be applied to render the path to a graphics context. ### `path.moveTo(x, y)` Moves the virtual pen to the given x, y coordinates. ### `path.lineTo(x, y)` Adds a line to the path from the current point to the given x, y coordinates. ### `path.quadraticCurveTo(cpx, cpy, x, y)` Adds a quadratic curve to the path from the current point to the given x, y coordinates using cpx, cpy as a control point. ### `path.bezierCurveTo(cp1x, cp1y, cp2x, cp2y, x, y)` Adds a bezier curve to the path from the current point to the given x, y coordinates using cp1x, cp1y and cp2x, cp2y as control points. ### `path.closePath()` Closes the current sub-path by drawing a straight line back to the starting point. ### `path.toFunction()` Compiles the path to a JavaScript function that can be applied with a graphics context in order to render the path. ### `path.toSVG()` Converts the path to an SVG path data string. ### `path.bbox` This property represents the path’s bounding box, i.e. the smallest rectangle that contains the entire path shape. This is the exact bounding box, taking into account control points that may be outside the visible shape. ### `path.cbox` This property represents the path’s control box. It is like the bounding box, but it includes all points of the path, including control points of bezier segments. It is much faster to compute than the real bounding box, but less accurate if there are control points outside of the visible shape. ## Subsets Fontkit can perform font subsetting, i.e. the process of creating a new font from an existing font where only the specified glyphs are included. This is useful to reduce the size of large fonts, such as in PDF generation or for web use. Currently, subsets produce minimal fonts designed for PDF embedding that may not work as standalone files. They have no cmap tables and other essential tables for standalone use. This limitation will be removed in the future. You create a Subset object by calling `font.createSubset()`, described above. The API on Subset objects is as follows. ### `subset.includeGlyph(glyph)` Includes the given glyph object or glyph ID in the subset. ### `subset.encodeStream()` Returns a [stream](https://nodejs.org/api/stream.html) containing the encoded font file that can be piped to a destination, such as a file. ## License [MIT](https://choosealicense.com/licenses/mit/) pdfjs-LICENSE.txt Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS standard-fonts-FOXIT.txt // Copyright 2014 PDFium Authors. All rights reserved. // // Redistribution and use in source and binary forms, with or without // modification, are permitted provided that the following conditions are // met: // // * Redistributions of source code must retain the above copyright // notice, this list of conditions and the following disclaimer. // * Redistributions in binary form must reproduce the above // copyright notice, this list of conditions and the following disclaimer // in the documentation and/or other materials provided with the // distribution. // * Neither the name of Google Inc. nor the names of its // contributors may be used to endorse or promote products derived from // this software without specific prior written permission. // // THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS // "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT // LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR // A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT // OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, // SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT // LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, // DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY // THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT // (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE // OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. standard-fonts-LIBERATION.txt Digitized data copyright (c) 2010 Google Corporation with Reserved Font Arimo, Tinos and Cousine. Copyright (c) 2012 Red Hat, Inc. with Reserved Font Name Liberation. This Font Software is licensed under the SIL Open Font License, Version 1.1. This license is copied below, and is also available with a FAQ at: http://scripts.sil.org/OFL SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007 PREAMBLE The goals of the Open Font License (OFL) are to stimulate worldwide development of collaborative font projects, to support the font creation efforts of academic and linguistic communities, and to provide a free and open framework in which fonts may be shared and improved in partnership with others. The OFL allows the licensed fonts to be used, studied, modified and redistributed freely as long as they are not sold by themselves. The fonts, including any derivative works, can be bundled, embedded, redistributed and/or sold with any software provided that any reserved names are not used by derivative works. The fonts and derivatives, however, cannot be released under any other type of license. The requirement for fonts to remain under this license does not apply to any document created using the fonts or their derivatives. DEFINITIONS "Font Software" refers to the set of files released by the Copyright Holder(s) under this license and clearly marked as such. This may include source files, build scripts and documentation. "Reserved Font Name" refers to any names specified as such after the copyright statement(s). "Original Version" refers to the collection of Font Software components as distributed by the Copyright Holder(s). "Modified Version" refers to any derivative made by adding to, deleting, or substituting ? in part or in whole ? any of the components of the Original Version, by changing formats or by porting the Font Software to a new environment. "Author" refers to any designer, engineer, programmer, technical writer or other person who contributed to the Font Software. PERMISSION & CONDITIONS Permission is hereby granted, free of charge, to any person obtaining a copy of the Font Software, to use, study, copy, merge, embed, modify, redistribute, and sell modified and unmodified copies of the Font Software, subject to the following conditions: 1) Neither the Font Software nor any of its individual components,in Original or Modified Versions, may be sold by itself. 2) Original or Modified Versions of the Font Software may be bundled, redistributed and/or sold with any software, provided that each copy contains the above copyright notice and this license. These can be included either as stand-alone text files, human-readable headers or in the appropriate machine-readable metadata fields within text or binary files as long as those fields can be easily viewed by the user. 3) No Modified Version of the Font Software may use the Reserved Font Name(s) unless explicit written permission is granted by the corresponding Copyright Holder. This restriction only applies to the primary font name as presented to the users. 4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font Software shall not be used to promote, endorse or advertise any Modified Version, except to acknowledge the contribution(s) of the Copyright Holder(s) and the Author(s) or with their explicit written permission. 5) The Font Software, modified or unmodified, in part or in whole, must be distributed entirely under this license, and must not be distributed under any other license. The requirement for fonts to remain under this license does not apply to any document created using the Font Software. TERMINATION This license becomes null and void if any of the above conditions are not met. DISCLAIMER THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM OTHER DEALINGS IN THE FONT SOFTWARE. NotoSans-OFL.txt Copyright 2018 The Noto Project Authors (github.com/googlei18n/noto-fonts) This Font Software is licensed under the SIL Open Font License, Version 1.1. This license is copied below, and is also available with a FAQ at: http://scripts.sil.org/OFL ----------------------------------------------------------- SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007 ----------------------------------------------------------- PREAMBLE The goals of the Open Font License (OFL) are to stimulate worldwide development of collaborative font projects, to support the font creation efforts of academic and linguistic communities, and to provide a free and open framework in which fonts may be shared and improved in partnership with others. The OFL allows the licensed fonts to be used, studied, modified and redistributed freely as long as they are not sold by themselves. The fonts, including any derivative works, can be bundled, embedded, redistributed and/or sold with any software provided that any reserved names are not used by derivative works. The fonts and derivatives, however, cannot be released under any other type of license. The requirement for fonts to remain under this license does not apply to any document created using the fonts or their derivatives. DEFINITIONS "Font Software" refers to the set of files released by the Copyright Holder(s) under this license and clearly marked as such. This may include source files, build scripts and documentation. "Reserved Font Name" refers to any names specified as such after the copyright statement(s). "Original Version" refers to the collection of Font Software components as distributed by the Copyright Holder(s). "Modified Version" refers to any derivative made by adding to, deleting, or substituting -- in part or in whole -- any of the components of the Original Version, by changing formats or by porting the Font Software to a new environment. "Author" refers to any designer, engineer, programmer, technical writer or other person who contributed to the Font Software. PERMISSION & CONDITIONS Permission is hereby granted, free of charge, to any person obtaining a copy of the Font Software, to use, study, copy, merge, embed, modify, redistribute, and sell modified and unmodified copies of the Font Software, subject to the following conditions: 1) Neither the Font Software nor any of its individual components, in Original or Modified Versions, may be sold by itself. 2) Original or Modified Versions of the Font Software may be bundled, redistributed and/or sold with any software, provided that each copy contains the above copyright notice and this license. These can be included either as stand-alone text files, human-readable headers or in the appropriate machine-readable metadata fields within text or binary files as long as those fields can be easily viewed by the user. 3) No Modified Version of the Font Software may use the Reserved Font Name(s) unless explicit written permission is granted by the corresponding Copyright Holder. This restriction only applies to the primary font name as presented to the users. 4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font Software shall not be used to promote, endorse or advertise any Modified Version, except to acknowledge the contribution(s) of the Copyright Holder(s) and the Author(s) or with their explicit written permission. 5) The Font Software, modified or unmodified, in part or in whole, must be distributed entirely under this license, and must not be distributed under any other license. The requirement for fonts to remain under this license does not apply to any document created using the Font Software. TERMINATION This license becomes null and void if any of the above conditions are not met. DISCLAIMER THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM OTHER DEALINGS IN THE FONT SOFTWARE.