feat: allow asking for using xref streams, which opens the option to build very large files #291
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…build very large files
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Enable using Xref streams for regular PDF files (and not just modified files, as it was). To do this provide StartPDF/StartPDFForStream with PDFCreationSettings which inWriteXrefAsXrefStream is true. You should also aim for PDFVersion of 1.5 or higher (the last one is more for the sake of readers as xref streams are a 1.5 feature (or higher).
See XrefStreamsTest.cpp for an example.
What this allows is to lift the limit of 10gbs for file size imposed by regular xrefs that use 10 decimal digits to describe file offset. You can now use the full long long kind of size (~8 EBs or ~8K TBs).