Ghostscript 9.26 does not set bounding box correctly

Bug #1830496 reported by Andrew G
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ghostscript (Ubuntu)
New
Undecided
Unassigned

Bug Description

Ghostscript 9.26 in Ubuntu 18.04 LTS has a bug which causes wrongly sized boundary boxes in output from epstool. This appears to a single-line typing mistake that has been fixed in Ghostscript 9.27. Could Ghostscript 9.26 (used in 18.04 LTS) be patched?

Details of bug and fix are here:
https://bugs.ghostscript.com/show_bug.cgi?id=700306

Bug 700306: Fix values returned by bbox device.

    The "any part of a pixel" code in the new scan converter holds a
    "cursor" position that determines where edges intersect with
    the scanlines. The leftmost and rightmost positions of intersection
    are held in this as values of type fixed.

    The "null" cursor position is represented by using maximal/minimal
    values. Unfortunately, I used {max,min}_int_in_fixed, rather than
    {max,min}_fixed, which meant they weren't nearly as maximal/minimal
    as they ought to have been.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.