Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use pdfrw instead of editing PDF files directly #516

Merged
merged 13 commits into from
Oct 5, 2017
Merged

Use pdfrw instead of editing PDF files directly #516

merged 13 commits into from
Oct 5, 2017

Commits on Sep 4, 2017

  1. Use pdfrw to edit PDF metadata and test them

    @liZe
    liZe committed Sep 4, 2017
    Configuration menu
    Copy the full SHA
    f29d23b View commit details
    Browse the repository at this point in the history

Commits on Sep 5, 2017

  1. Add support of marks and bleed pages properties 

    Fix #471.
    @liZe
    liZe committed Sep 5, 2017
    Configuration menu
    Copy the full SHA
    71d5409 View commit details
    Browse the repository at this point in the history

  2. Fix bleedbox translation for multiple pages

    @liZe
    liZe committed Sep 5, 2017
    Configuration menu
    Copy the full SHA
    5ce24fd View commit details
    Browse the repository at this point in the history

Commits on Sep 6, 2017

  1. Fix test failing with old versions of cairo

    @liZe
    liZe committed Sep 6, 2017
    Configuration menu
    Copy the full SHA
    09fda5f View commit details
    Browse the repository at this point in the history

Commits on Sep 21, 2017

  1. Added support to work with bleed like padding (bleed-top/right/bottom… 

    …/left)
    @dark-light-cz
    dark-light-cz committed Sep 21, 2017
    Configuration menu
    Copy the full SHA
    05446f5 View commit details
    Browse the repository at this point in the history

Commits on Oct 4, 2017

  1. Fix import order

    @liZe
    liZe committed Oct 4, 2017
    Configuration menu
    Copy the full SHA
    112c3fc View commit details
    Browse the repository at this point in the history

  2. Use bytes for PDF compressed files streams 

    Cleans code and fixes Python 2 support.
    @liZe
    liZe committed Oct 4, 2017
    Configuration menu
    Copy the full SHA
    c81c973 View commit details
    Browse the repository at this point in the history

Commits on Oct 5, 2017

  1. Merge pull request #517 from dark-light-cz/pdfrw 

    Added support to work with bleed like padding (bleed-top/right/bottom…
    @liZe
    liZe authored Oct 5, 2017
    Configuration menu
    Copy the full SHA
    34153d2 View commit details
    Browse the repository at this point in the history

  2. Fix tests randomly broken because of unordered dicts used by pdfrw

    @liZe
    liZe committed Oct 5, 2017
    Configuration menu
    Copy the full SHA
    6865415 View commit details
    Browse the repository at this point in the history

  3. Add tests for bleed

    @liZe
    liZe committed Oct 5, 2017
    Configuration menu
    Copy the full SHA
    09bd0a3 View commit details
    Browse the repository at this point in the history

  4. Cleanups

    @liZe
    liZe committed Oct 5, 2017
    Configuration menu
    Copy the full SHA
    e5dcab7 View commit details
    Browse the repository at this point in the history

  5. Use a specific function to test that 2 PDFs are equivalent 

    We have to compare various PDF objects to compare PDF files as pdfrw doesn't
produce the same PDF files from the same input. That's caused by Python's
unordered dicts. Comparing pdf bytes thus works with Python 3.6+ where dicts
are ordered.
    @liZe
    liZe committed Oct 5, 2017
    Configuration menu
    Copy the full SHA
    f64feae View commit details
    Browse the repository at this point in the history

  6. Remove the Python 3.6 fast path in PDF comparison for tests 

    Even if it's not officially documented, dicts are ordered in Python 3.6. We
relied on this to assert that PDF generation was reproducible, it works on some
versions of Python 3.6 but not on Travis for some reason.
    @liZe
    liZe committed Oct 5, 2017
    Configuration menu
    Copy the full SHA
    0ec7614 View commit details
    Browse the repository at this point in the history