Summary: | problem with redirect output of gs api to stdout | ||
---|---|---|---|
Product: | Ghostscript | Reporter: | vg <vguedes> |
Component: | Client API | Assignee: | Default assignee <ghostpdl-bugs> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | alex |
Priority: | P4 | ||
Version: | 9.05 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Customer: | Word Size: | --- |
Description
vg
2012-08-28 19:28:51 UTC
TIFF format depends on offsets to access various data tables. Usually, the offsets are known only when all the data are consumed and compressed. Only uncompressed files can have all the offsets calculated in advance. Ghostscript uses libTiff to write TIFF files. libTiff is not designed for this special case and always requires direct access to the output file. Changing libTiff to use sequential access to uncompressed files is difficult, and beyond the control of Ghostscript developers. You need to use a file format, that can be generated sequentially, for instance PNM format, instead of TIFF. Thank for your quickly answer. Ok. In this case, I think the generated tiff isn't compressed. And I don't understand why it works when I redirect the stdout to a file or pipe to echo in command line context. (In reply to comment #1) > TIFF format depends on offsets to access various data tables. Usually, the > offsets are known only when all the data are consumed and compressed. > Only uncompressed files can have all the offsets calculated in advance. > > Ghostscript uses libTiff to write TIFF files. libTiff is not designed > for this special case and always requires direct access to the output file. > > Changing libTiff to use sequential access to uncompressed files is difficult, > and beyond the control of Ghostscript developers. > You need to use a file format, that can be generated sequentially, for instance > PNM format, instead of TIFF. |