You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since PDF 1.5, cross-reference streams can be used instead of cross-reference tables.
Since streams can be compressed it helps reducing the PDF file size.
XRef streams will also allow to use features like object streams in the future
The text was updated successfully, but these errors were encountered:
Where in fpdf2-produced PDF documents do you think that cross-reference streams could/should be used?
Cross-reference streams replace the normal cross-reference.
The normal cross-refence table looks like this:
xref
0 21
0000000000 65535 f
0000000009 00000 n
0000000096 00000 n
0000000199 00000 n
0000000280 00000 n
0000000446 00000 n
0000000584 00000 n
0000000808 00000 n
0000001406 00000 n
0000001475 00000 n
0000001687 00000 n
0000001950 00000 n
0000004839 00000 n
0000004988 00000 n
0000005275 00000 n
0000006056 00000 n
0000006126 00000 n
0000006347 00000 n
0000006624 00000 n
0000012282 00000 n
0000012381 00000 n
When you use cross-reference streams you can also use object streams. I used it in the past to get all my bookmarks (outlines) objects and put them all inside a compressed stream. It was an extreme case but for very large PDF files it helps you produce smaller files.
When you use cross-reference streams you can also use object streams. I used it in the past to get all my bookmarks (outlines) objects and put them all inside a compressed stream. It was an extreme case but for very large PDF files it helps you produce smaller files.
OK
They yeah, fpdf2 would welcome such feature if someone is willing to implement it!
Since PDF 1.5, cross-reference streams can be used instead of cross-reference tables.
Since streams can be compressed it helps reducing the PDF file size.
XRef streams will also allow to use features like object streams in the future
The text was updated successfully, but these errors were encountered: