Fixed issues with margins

.eslintrc.js

@@ -1,18 +1,21 @@
 module.exports = {
-    "env": {
-        "browser": true,
-        "commonjs": true,
-        "es6": true,
-        "node": true
-    },
-    "extends": "eslint:recommended",
-    "globals": {
-        "Atomics": "readonly",
-        "SharedArrayBuffer": "readonly"
-    },
-    "parserOptions": {
-        "ecmaVersion": 2018
-    },
-    "rules": {
-    }
-};
+  parser: "@typescript-eslint/parser",
+  extends: ["eslint:recommended", "plugin:@typescript-eslint/recommended"],
+  env: {
+    browser: true,
+    commonjs: true,
+    es6: true,
+    node: true,
+    jasmine: true
+  },
+  plugins: ["@typescript-eslint", "jasmine"],
+  globals: {
+    Atomics: "readonly",
+    SharedArrayBuffer: "readonly"
+  },
+  parserOptions: {
+    ecmaVersion: 2018,
+    sourceType: "module"
+  },
+  rules: {}
+};

.github/workflows/npm-publish.yml

@@ -0,0 +1,22 @@
+# This workflow will run tests using node and then publish a package to GitHub Packages when a release is created
+# For more information see: https://help.github.com/actions/language-and-framework-guides/publishing-nodejs-packages
+
+name: Node.js Package
+
+on:
+  release:
+    types: [published]
+
+jobs:
+  publish-npm:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-node@v1
+        with:
+          node-version: 12
+          registry-url: https://registry.npmjs.org/
+      - run: npm ci
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: ${{secrets.NPM_TOKEN}}

.github/workflows/stale.yml

@@ -0,0 +1,21 @@
+name: Mark and close stale issues
+
+on:
+  schedule:
+  - cron: "30 1 * * *"
+
+jobs:
+  stale:
+
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/stale@v3
+      with:
+        repo-token: ${{ secrets.GITHUB_TOKEN }}
+        stale-issue-message: 'This issue is stale because it has been open 90 days with no activity. It will be closed soon. Please comment/reopen if this issue is still relevant.'
+        stale-issue-label: 'no-issue-activity'
+        exempt-issue-labels: 'Bug,Feature Request,persistent'
+        remove-stale-when-updated: true
+        days-before-stale: 90
+        days-before-close: 7

.gitpod.yml

@@ -1,5 +1,5 @@
 tasks:
-  - init: npm run build
+  - init: npm install && npm run build
     command: npm start
 ports:
   - port: 8000

.travis.yml

@@ -5,6 +5,8 @@ install:
   - npm -g install yarn
   - yarn
 cache:
+  npm: false
+  yarn: false
   directories:
-    - ~/.yarn
+#    - ~/.yarn
     - ~/.nvm

CONTRIBUTING.md

@@ -0,0 +1,80 @@
+# Contribution Guidelines
+
+:+1::tada: First off, thanks for taking the time to contribute! :tada::+1:
+
+## Code of Conduct
+
+This project and everyone participating in it is governed by the
+[Code of Conduct](https://github.com/MrRio/jsPDF/blob/master/CODE_OF_CONDUCT.md).
+By participating, you are expected to uphold this code. Please report unacceptable behavior to
+[[email protected]](mailto:[email protected]).
+
+## How Can I Contribute?
+
+jsPDF is an open source project and requires help from the community. Any contributions from the community are very
+much welcome! Be it "only" reporting bugs or actually contributing code to the repository.
+
+### Reporting Bugs
+
+jsPDF is by no means perfect. If you find something is not working as expected we are glad to receive an
+issue report from you. Please make sure to
+[search for similar issues](https://github.com/search?q=is%3Aissue+repo%3AMrRio%2FjsPDF&type=issues) first.
+
+If you did not find any related issues, please report a [new issue](https://github.com/MrRio/jsPDF/issues).
+In order to be able to react efficiently we ask you to provide us with the following information:
+
+- The **version** of jsPDF you are using
+- A small code example that reproduces the issue ([mcve](https://stackoverflow.com/help/mcve))
+
+Please also abide to these rules:
+
+- Formulate the issue in English.
+- Provide a **clear and descriptive** title
+- Stick to the issue template
+- Make sure code is properly indented and
+  [formatted](https://help.github.com/articles/basic-writing-and-formatting-syntax/#quoting-code) (Use ``` around
+  code blocks). Attach large code snippets as file.
+
+Note that this is an open source project and don't expect us to fix every issue immediately. Please also consider
+fixing the issue yourself and preparing a pull request. Sometimes a pointer to a specific line of code already helps
+a lot. We will happily discuss and merge contributions from the community!
+
+### Pull requests
+
+We are very happy about pull requests from the community and will discuss and merge them in a timely manner. When
+preparing a pull request please follow these guidelines:
+
+- You can find instructions for building and testing jsPDF [below](#building-and-testing-jspdf)
+- Make sure to cover new features or bugs with test cases. Test cases should be as small as possible.
+- Make sure to follow the PDF specification. JsPDF currently implements part of the PDF 1.3 specification.
+- Make sure all tests are green before committing (`npm run test-local`)
+- Use only es5-compatible code in the `src` folder (except for import/export statements). The sources are currently
+  not babeled. When using newer EcmaScript or Browser APIs make sure the required polyfills are listed in
+  `src/polyfills.js`.
+- Run `npm run prettier` before committing.
+- For the commit message, follow these guidelines:
+  - Use the present tense ("Add feature" not "Added feature")
+  - Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
+  - Limit the first line to 72 characters or fewer
+  - Reference issues and pull requests liberally after the first line
+- Make sure the CI tests are green after pushing. If not, please fix them.
+
+### Building and Testing jsPDF
+
+You can build the library with `npm install && npm run build`. This will fetch all dependencies and then compile the `dist`
+files. To see the examples locally you can start a web server with `npm start` and go to `localhost:8000`.
+
+To test locally, run
+
+```sh
+npm run test-unit # will run only unit tests
+# or
+npm run test-local # will also run deployment tests for different module formats using the files in the dist folder
+```
+
+The tests live in the `test` folder and are a set of `specs` that sometimes compare the result with checked-in
+reference PDF files. New reference PDFs can be created by running `npm run test-training` in the background.
+
+Alternatively, you can build jsPDF using these commands in a readily configured online workspace:
+
+[![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io#https://github.com/MrRio/jsPDF)

HOTFIX_README.md

@@ -1,53 +1,66 @@
-#Hotfixes
+# Hotfixes
 
 We sometimes bake-in solutions (A.K.A. hotfixes) to solve issues for specific use cases.
 
 When we deem a hotfix will not break existing code,
- will make it default behaviour and mark the hotfix as _accepted_,
- At that point the define can be removed.
-
- To enable a hotfix, define the following member of your created PDF,
-where the pdf.hotfix field is the name of the hotfix.
-
-    var pdf new jsPDF(...);
-    pdf.hotfix.fill_close = true;
-
+will make it default behaviour and mark the hotfix as _accepted_,
+At that point the define can be removed.
+
+To enable a hotfix, pass the `hotfixes` option to the jsPDF constructor:
+
+```js
+new jsPDF({
+  hotfixes: ["px_scaling"]
+});
+```
+
 # Active Hotfixes
+
 ## px_scaling
 
 ### Applies To
+
 jsPDF Core
 
 ### Description
+
 When supplying 'px' as the unit for the PDF, the internal scaling factor was being miscalculated making drawn components
-larger than they should be.  Enabling this hotfix will correct this scaling calculation and items will be drawn to the
+larger than they should be. Enabling this hotfix will correct this scaling calculation and items will be drawn to the
 correct scale.
 
 ### To Enable
+
 To enable this hotfix, supply a 'hotfixes' array to the options object in the jsPDF constructor function, and add the
 string 'px_scaling' to this array.
 
 #Accepted Hotfixes
+
 ## scale_text
 
 ### Applies To
+
 context2d plugin
 
 ### Affects
+
 Drawing and Filling Text when a scale transformation is active.
 
 ### Description
+
 jsPDF currently has no way to draw scaled text.  
 This hotfix scales the current font size by the x-axis scale factor.
- 
+
 ## fill_close
+
 ### Applies To
+
 context2d plugin
 
 ### Affects
-Filling paths 
+
+Filling paths
 
 ### Description
+
 In certain cases, closing a fill would result in a path resolving to an incorrect point.
-The was most likely fixed when we refactored matrix logic.  Enabling this hotfix will ignore a most-likely unneeded workaround.
-
+The was most likely fixed when we refactored matrix logic. Enabling this hotfix will ignore a most-likely unneeded workaround.

ISSUE_TEMPLATE.md

@@ -1,5 +1,7 @@
 Feature requests, bug reports etc. are very welcome as issues. But questions are directed to stackoverflow with the tag `jspdf`.
 
+If you are facing issues with utf-8 characters, please refer to [#2677](https://github.com/MrRio/jsPDF/issues/2677).
+
 Note that bug reports should follow these guidelines:
 
 1. A bug should be reported as an [mcve](https://stackoverflow.com/help/mcve)

MIT-LICENSE.txt → LICENSE

@@ -1,4 +1,6 @@
-Copyright (c) 2010-2016 James Hall, https://github.com/MrRio/jsPDF
+Copyright
+(c) 2010-2020 James Hall, https://github.com/MrRio/jsPDF
+(c) 2015-2020 yWorks GmbH, https://www.yworks.com/
 
 Permission is hereby granted, free of charge, to any person obtaining
 a copy of this software and associated documentation files (the