Public bug reported:

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.

** Affects: ghostscript (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ghostscript in Ubuntu.
https://bugs.launchpad.net/bugs/1830496

Title:
  Ghostscript 9.26 does not set bounding box correctly

Status in ghostscript package in Ubuntu:
  New

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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1830496/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to