Summary: | -dEPSCrop depends on EPSF-3.0 header? | ||
---|---|---|---|
Product: | Ghostscript | Reporter: | Hin-Tak Leung <htl10> |
Component: | Documentation | Assignee: | Ray Johnston <ray.johnston> |
Status: | RESOLVED WORKSFORME | ||
Severity: | enhancement | CC: | christinedelight.top85 |
Priority: | P4 | ||
Version: | 8.61 | ||
Hardware: | PC | ||
OS: | Linux | ||
Customer: | Word Size: | --- |
Description
Hin-Tak Leung
2008-02-27 11:47:34 UTC
This is not a bug in that EPSCrop is intended to only do something for DSC compliant EPSF files, with the appropriate header. Producing images by first running a bbox on the file is something that requires two passes on the file, and since it would slow things down, we don't want to do it. The section in doc/Use.htm _does_ mention Document Structuring Conventions (DSC) but this could be improved slightly by adding a reference to Adobe's document on DSC and explaining that EPSCrop and EPSFitPage ONLY apply to DSC compliant EPSF files. I don't think Ken should be bothered with this. Yes, I checked the actual code and it checks for "%!PS-Adobe-a.b EPSF-c.d" headers; and the documentation did mention in doc/Use.htm#EPS that it needs to be DSC compliant; however I think it is appropriate and relevant to briefly mention DSC compliantness at the beginning of doc/Use.htm#EPS_parameters also? Oh, the fact that it requires two passes mean that this option does not work with pipes, right? Should mention that if that's the case.... The doc/Use.htm has this statement which should be sufficient: An EPS file must conform to the Document Structuring Conventions |