Bo

Hi @xaizek , Thank for putting this together. I've been deep into maintaining a different project but I hope to have time to look into this today 👍

Hi @xaizek , Thanks for the feature, but I have to admit I bumped into some issues when trying to use it. Because the `clang_complete_continue` isn't recognized by the main...

👍 for making this part of the master branch. #### As to backwards compatibility: A backwards compatible solution must conform to the following property: Anything placed in the `.clang_complete` plugin...

Hi @rdunlop , Thank you for opening this issue. I totally understand your concern and I myself was debating this change for his very reason. This isn't about a performance...

Hi @FriscoTony , Thanks for the PR . I agree that the handling of PDF info / metadata could be vastly improved and I am thankful for your work and...

Hi @dskim , Could you send me a PDF, so I could reproduce the issue and test solutions? Thanks, Bo. P.S. **Workaround**: for now, it should be possible to work...

Hi @Laykou Thank you for opening this issue. Please note my comments: [here for issue #185](https://github.com/boazsegev/combine_pdf/issues/185#issuecomment-768270331) and [here for issue #191](https://github.com/boazsegev/combine_pdf/issues/191#issuecomment-815336809). I usually prefer lax parsers that allow formatting errors...

Sorry, busy days... I'll look it over soon... I hope.

This shouldn't be a version related warning... it should come up only for certain PDF files where parsing might be only partially supported (due to compression and encryption concerns), warning...

@igbanam , thanks for adding your knowledge to the discussion. Could you send me and example PDF that doesn't work? one where you experience data-loss when opening using CombinePDF? I'll...