diff options
| author | Ken Sharp <ken.sharp@artifex.com> | 2022-08-31 15:03:43 +0100 |
|---|---|---|
| committer | Ken Sharp <ken.sharp@artifex.com> | 2022-08-31 15:04:12 +0100 |
| commit | 22ed83c9f608b66194aba0453c444f9aa284f9aa (patch) | |
| tree | d015cadad8b9043adc2e46c79f76d2070ba4d3a1 /doc | |
| parent | 78fd499115daa28dfb51f0f464c9ce009648fd08 (diff) | |
| download | ghostpdl-22ed83c9f608b66194aba0453c444f9aa284f9aa.tar.gz | |
Documentation - Add a note about precision of the bbox device
Bug #705830 "imprecise bbox of PDF"
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/Devices.htm | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/Devices.htm b/doc/Devices.htm index 60c60776a..214aa54fe 100644 --- a/doc/Devices.htm +++ b/doc/Devices.htm @@ -1978,6 +1978,14 @@ pixels, e.g.,</p> gs -dNOPAUSE -dBATCH -sDEVICE=bbox -r100 -g500000x500000 </code></blockquote> +<p> +The box returned by the bbox device is just sufficient to contain the pixels which would be rendered by +Ghostscript at the selected resolution. The language rendering rules can mean this differs by up to two pixels from +the 'theoretical' area covered, and the precise area covered by curves and line joins is also, to some +extent, related to the resolution. Finally the actual pixel position needs to be converted back to +PostScript points, and that can be affected by mathematical precision, which can cause rounding errors. +As a result the bounding box returned may differ very slightly from that which was expected. +</p> <h3><a name="Ink_coverage_output"></a>Ink coverage output</h3> <p> |