| Summary: | [PATCH] Add -noannotate option in pdftocairo to disable annotations | ||
|---|---|---|---|
| Product: | poppler | Reporter: | Stephen E. <bhs2007> |
| Component: | utils | Assignee: | poppler-bugs <poppler-bugs> |
| Status: | RESOLVED MOVED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | Patch to add -noannotate option to pdftocairo | ||
Instead of an option for turning off annotations I would prefer a more general option for controlling annotations. The glib api has print options: * POPPLER_PRINT_DOCUMENT: print main document contents * POPPLER_PRINT_MARKUP_ANNOTS: print document and markup annotations * POPPLER_PRINT_STAMP_ANNOTS_ONLY: print document and only stamp annotations * POPPLER_PRINT_ALL: print main document contents and all markup annotations We could adde a "-annotate=xxx" type of option. eg -annotate=[none|markup|stamp|all] with the default (when -annotate is not specified) to print no annotations. I'm not sure if it would also be useful to be able to specify a list of specific annotations. eg -annotate=watermark,printermark,trapnet But this could easily be added later if someone found a need for it. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/poppler/poppler/issues/484. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 121977 [details] Patch to add -noannotate option to pdftocairo I was looking for a way to prevent pdftocairo from drawing PDF form fields when rendering to a bitmap, and came up short. The attached patch adds a -noannotate flag which does this. (Thanks to jcrain from IRC for pointing me toward the appropriate internals!)