Iterating over all content of all pages? #1160
-
|
I would like to use pdfcpu for doing my own analysis of all the content of a PDF, but it seems the API does not support this kind of low-level PDF processing, or am I overlooking something? Does the API allow me to do something like:
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 3 replies
-
|
I have no idea what you are up to but you can do anything you want. |
Beta Was this translation helpful? Give feedback.
-
|
I am looking for the API calls to not only iterate over pages, but also over the page content. For instance, I want to find rectangles on each page, without having to parse the streams myself. If that can't be done with the API, I would be relying on internals of the package which is usually a bad idea. |
Beta Was this translation helpful? Give feedback.
-
|
Page content stream internals are not modelled by pdfcpu as page content is not really processed other than for resource optimization. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the fast response. |
Beta Was this translation helpful? Give feedback.
-
|
The only time pdfcpu touches the page content stream to optimize resources like images, fonts, and color spaces.To remove unused objects or compress streams to reduce file size. |
Beta Was this translation helpful? Give feedback.
-
|
You might want to look at qpdf, which can create a fairly complete json representation of a pdf. If you are trying to do this programatically within go, you could spawn a process, read its output, and unmarshal it. Not very elegant, I know. |
Beta Was this translation helpful? Give feedback.
Page content stream internals are not modelled by pdfcpu as page content is not really processed other than for resource optimization.