Summary: | vector devices close output file incorrectly | ||
---|---|---|---|
Product: | Ghostscript | Reporter: | Russell Lang <gsview> |
Component: | Graphics Library | Assignee: | Russell Lang <gsview> |
Status: | NOTIFIED FIXED | ||
Severity: | normal | CC: | igor.melichev |
Priority: | P2 | ||
Version: | master | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Customer: | Word Size: | --- | |
Bug Depends on: | |||
Bug Blocks: | 687542 |
Description
Russell Lang
2004-07-06 04:01:18 UTC
pdfwrite, being a vector device, considers the output file as a positionable one. It won't work with a pipe. It works with pdfwrite for simple files! The main requirement here is for use with pswrite. To print PDF files it is common to convert to PS with pswrite then send to a PS printer. Apart from the pipe issue, does the proposed change look correct? Any other unexpected side effects? This change looks valid. Igor's comment about the pdfwrite device requiring a 'seekable' file is not relevant since this is supposed to be taken into account by the caller to gdev_vector_open_file_options setting the VECTOR_OPEN_FILE_SEQUENTIAL in the open_options. This change looks valid. Igor's comment about the pdfwrite device requiring a 'seekable' file is not relevant since this is supposed to be taken into account by the caller to gdev_vector_open_file_options setting the VECTOR_OPEN_FILE_SEQUENTIAL in the open_options. Since gdevpdf.c uses gdev_vector_open_file which has the default options all 0, the file will be required to be seekable (since VECTOR_OPEN_FILE_SEQUENTIAL and VECTOR_OPEN_FILE_SEQUENTIAL_OK are false) |