Not sure anyone has applied the appropriate level of caution here, so just in case: be aware that this is a hidden preference for a reason! DT is trying to protect you from potentially corrupting a PDF file that it’s recognised might have a problem if you edit it. Now, this is only a might - the file could be fine after editing. But equally it might not be!
It’s of course fine to decide you don’t want DT to add safety rails like this, but I just wanted to clarify what decision you’re making so that you aren’t making a blind choice.
Thanks for the warning. I am usually not editing PDFs, not even highlighting or making annotations, but I like to indicate the origin of my PDF documents and I therefore add author, title and source, such as an archive reference in the PDF properties fields. I would be very astonished if PDFKit is not able to do that without corrupting the file, however, if it does happen, I will have to use PDF expert or some other PDF tool with their own PDF engine to make these additions. At the moment it saves me a lot of time and effort to be able to do it directly in DT and not have to call up any external application.
To both actually. The reason for that is that if I share the PDF with somebody they will not see the DT metadata for this PDF, but they can consult the PDF properties and can then see the origin of the document. In the metadata I add a lot more information when needed or available.