v5 release roadmap (testers wanted!) #341
Replies: 6 comments 9 replies
-
If there are no objections, I plan to merge |
Beta Was this translation helpful? Give feedback.
-
All right, I've merged the devel branch, and the first beta release has rolled out: To install, you can do e.g. Please test – thanks! |
Beta Was this translation helpful? Give feedback.
-
Over two weeks have passed, but there has not been any feedback yet. It seems like beta releases do not get much community attention. |
Beta Was this translation helpful? Give feedback.
-
Saw this now. I can add this to my test matrix for kreuzberg |
Beta Was this translation helpful? Give feedback.
-
I found one issue with the page flatten() function. Text extraction after flattening does not keep the correct reading order. The text from the fillable area is listed after all the general text, but it should keep the original order.
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Our development branch for the next major release (v5) is finally nearing a state at which it could be merged into
main
some time soon. Highlights include:PdfPosConv
/PdfBitmap.get_posconv(page)
to translate between page and bitmap coordinatesPdfObject.get_quad_points()
to get the corner positions of an image or text objectPdfImage.get_bitmap(render=True)
:scale_to_original
option to preserve the native pixel size and avoid resolution degradationPdfBookmark
andPdfDest
helpers replace the oldPdfOutlineItem
namedtuple--invert-lightness --exclude-images
to post-process with selective lightness inversion (this may be useful to achieve a "dark look" for light PDFs)See
docs/devel/changelog_staging.md
for more.The branch has been around for a rather long time now, and effectively away from end-user testing. While there are many improvements, it is also possible something may have broken/regressed.
That's why we'd like downstreams to try out the updated codebase and give feedback (taking into account the intentional API-breaking changes – see the changelog).
The plan is to make a beta release (or, if necessary, several beta releases) and wait for community response for at least 2 weeks (maybe more) before committing the actual release.
For the first few follow-up releases of the v5 series (e.g. 5.1 and 5.2), we reserve the right to apply API(-changing) corrections, should the need arise. After this, we endeavor to keep the helpers API stable as we did for v4, until the next major release.
Thanks for your attention.
Beta Was this translation helpful? Give feedback.
All reactions