DOC: merge_transformed_page()

[paternal]

There is no example for merge_transformed_page(), although several issues could have been avoided if such an example existed (#1630, #1426, and issues that users do not bother to open). This pull request adds such an example.

Thanks for your work!

-- Louis

[codecov]

Codecov Report

Base: 91.92% // Head: 91.92% // No change to project coverage 👍

Coverage data is based on head (7d6cb4f) compared to base (4e276b2).
Patch has no changes to coverable lines.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1647   +/-   ##
=======================================
  Coverage   91.92%   91.92%           
=======================================
  Files          33       33           
  Lines        6375     6375           
  Branches     1272     1272           
=======================================
  Hits         5860     5860           
  Misses        327      327           
  Partials      188      188           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[pubpub-zz]

@paternal
Thanks for you contribution. I would more likely recommend to use .merge_transformed_page() instead of doing the transform before merging. The advantage is that you can reuse the page.
we could keep the merge_page for the watermarking only.
Also maybe you could propose to update the example for underlay watermark using the over=False new option.

[paternal]

@paternal Thanks for you contribution. I would more likely recommend to use .merge_transformed_page() instead of doing the transform before merging.

Unless I misunderstood you, it is already done that way: since most of the examples on this page use merge_page(), I started with a naïve solution using this, that does not work. I then explain why it does not work, and I go on with the right solution using merge_transformed_page().

The advantage is that you can reuse the page. we could keep the merge_page for the watermarking only. Also maybe you could propose to update the example for underlay watermark using the over=False new option.

This page? https://pypdf.readthedocs.io/en/stable/user/add-watermark.html?highlight=watermark
I can update it.

[pubpub-zz]

@paternal Thanks for you contribution. I would more likely recommend to use .merge_transformed_page() instead of doing the transform before merging.

Unless I misunderstood you, it is already done that way: since most of the examples on this page use merge_page(), I started with a naïve solution using this, that does not work. I then explain why it does not work, and I go on with the right solution using merge_transformed_page().

I did not read correctly your proposal with the diff mod of github 🤭
I've seen so many people using transformation, that is currently not applying any changes on the annots.

The advantage is that you can reuse the page. we could keep the merge_page for the watermarking only. Also maybe you could propose to update the example for underlay watermark using the over=False new option.

This page? https://pypdf.readthedocs.io/en/stable/user/add-watermark.html?highlight=watermark I can update it.

yes🙂

[paternal]

Done.

English is not my first language: feel free to rephrase everything.

[MartinThoma]

hahaha, I love it 😄 ❤️

[MartinThoma]

@paternal Thank you 🙏

If you want, I can add you to the contributors page: https://pypdf.readthedocs.io/en/latest/meta/CONTRIBUTORS.html
Just let me know which name I should use :-) (just Louis? paternal?)

[paternal]

Just let me know which name I should use :-) (just Louis? paternal?)

Louis Paternault https://framagit.org/spalax

Thanks

[MartinThoma]

done :-)