Setting Redaction Code vs. Custom Text

[mwade-noetic]

I am creating redactions, but not burning them into, they show up as crossed out text. In Acrobat Pro, in the Redaction properties there are two properties that contain the text the will be placed into the redaction: "Custom Text" and "Redaction Code". The screen shot below is an example of that.

I cannot figure out how to set the "Redaction Code" vs. the Custom Text. Using the standard way of setting the redaction box text, it shows up this way. Is there a way to set it as "redaction code" instead? This would allow the users to review and accept the annotations with less work.

Currently I am calling "add_redact_annot() and setting text="redaction text". Perhaps I do this with a custom entry in the annotation info dictionary? I am setting the "content" to the redaction code as well there.

Thanks for any help.

[JorjMcKie]

I don't knows what Adobe means by redaction code. It is not part of the official set of dictionary keys of a redaction annotation.
In PyMuPDF, the "text" parameter is what will be put in the redact rectangle when applying, and therefore is the OverlayText.
You could look at the redaction definition after Adobe has been fiddling with it print(doc.xref_object(annot.xref)) and inspect where this ominous data has landed.

The problem here is like alays:
Annotations and fields are tool-specific when it comes to the technical implemementation, because there do not exist any rules that must be obeyed.
This implies:

• An annot made with some other tool, will look completely different after being updated with PyMuPDF. In addition, all original features are removed from the annot which PyMuPDF does not support.
• The opposite is also true: make an annot with PyMuPDF, then update it with e.g. Adobe and you will see drastic changes happening.

[mwade-noetic]

Thanks, I just realized in the last few minutes that they are importing an external set of codes that you can “Select” from a drop-down list below (in the screenshot) and use that to populate a code in the annotation. I thought they were pulling it from the annotation information itself when I first saw it. So in this case, they are just overlaying the annotation information with this custom external data that is external to the PDF itself. Thanks for the fast response! Michael Wade From: Jorj X. McKie ***@***.***> Sent: Saturday, January 29, 2022 1:40 AM To: pymupdf/PyMuPDF ***@***.***> Cc: Michael Wade ***@***.***>; Author ***@***.***> Subject: Re: [pymupdf/PyMuPDF] Setting Redaction Code vs. Custom Text (Discussion #1570) I don't knows what Adobe means by redaction code. It is not part of the official set of dictionary keys of a redaction annotation. In PyMuPDF, the "text" parameter is what will be put in the redact rectangle when applying, and therefore is the OverlayText. You could look at the redaction definition after Adobe has been fiddling with it print(doc.xref_object(annot.xref)) and inspect where this ominous data has landed. The problem here is like alays: Annotations and fields are tool-specific when it comes to the technical implemementation, because there do not exist any rules that must be obeyed. This implies: * An annot made with some other tool, will look completely different after being updated with PyMuPDF. In addition, all original features are removed from the annot which PyMuPDF does not support. * The opposite is also true: make an annot with PyMuPDF, then update it with e.g. Adobe and you will see drastic changes happening. — Reply to this email directly, view it on GitHub<#1570 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AS4L3SDET3RP4HTTKRCBPV3UYODTXANCNFSM5NCJBZCQ>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>