You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In particular, it would be useful, if stdin could be used to input a PDF file
and stdout to write the exported content.
This would enable PDF processing on the shell using pipes:
Hello!
Support for shell piping is a useful addition.
As far as your suggested addition to the extract command line processing I'd rather leave that up to the calling script.
I am also not in favour of using -o repeatedly within one command.
And if we're starting to use -o than that would have to change for all pdfcpu commands.
Hi,
Currently, when exporting PDF content it is only possible to specify the name of the directory
to which exported text files shall be written (outDir):
It would be very useful if it were possible to specify filenames instead:
Export all PDF pages to one file:
Export one page to file:
Export selected pages to the distinct files:
Export selected pages to the same file:
or
In particular, it would be useful, if stdin could be used to input a PDF file
and stdout to write the exported content.
This would enable PDF processing on the shell using pipes:
Read PDF input from stdin:
$ curl https://internet/some.pdf | pdfcpu extract -m content -o some_pages.txt -
Export text to stdout:
Best, Matthias
The text was updated successfully, but these errors were encountered: