View Revisions: Issue #1116
Summary | 0001116: Work around pdftocairo stdout bug | ||
---|---|---|---|
Revision | 2020-02-24 17:22 by rijkr | ||
Description | IST: "pdftocairo -png" is used to create SafePages images. On centos-release-7-7.1908.0.el7, pdftocairo 0.26.5 fails like this example:$ pdftocairo -png -r 24 -f 1 -l 1 -singlefile "a.pdf" - > "a.png" Error opening output file fd://0.png... although the manpage explains that "If the output-file is “-” , the output file will be written to stdout." Also see https://stackoverflow.com/questions/17231267/pdf-to-png-in-python-with-pdf2cairo SOLL: Probe "pdftocairo -v". If version is 0.26.5 then execute workaround statements. This default probe strategy can be overwritten with configuration property "system.host.cmd.pdftocairo.img.strategy": AUTO = use version probe (default), STREAM = use one (1) stdout/stdin stream command, SPLIT = split action into separate commands. |
||
Revision | 2020-02-22 19:53 by rijkr | ||
Description | IST: "pdftocairo -png" is used to create SafePages images. On centos-release-7-7.1908.0.el7, pdftocairo 0.26.5 fails like this example:$ pdftocairo -png -r 24 -f 1 -l 1 -singlefile "a.pdf" - > "a.png" Error opening output file fd://0.png... although the manpage explains that "If the output-file is “-” , the output file will be written to stdout." Also see https://stackoverflow.com/questions/17231267/pdf-to-png-in-python-with-pdf2cairo SOLL: Probe "pdftocairo -v". If version is 0.26.5 then execute workaround statements. |