bug-groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #50770] .PSPIC macro at bottom of page causes unwarranted page brea


From: Dave
Subject: [bug #50770] .PSPIC macro at bottom of page causes unwarranted page break
Date: Sun, 9 Apr 2017 15:38:56 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux i686; rv:45.0) Gecko/20100101 Firefox/45.0

URL:
  <http://savannah.gnu.org/bugs/?50770>

                 Summary: .PSPIC macro at bottom of page causes unwarranted
page break
                 Project: GNU troff
            Submitted by: barx
            Submitted on: Sun 09 Apr 2017 02:38:54 PM CDT
                Severity: 3 - Normal
              Item Group: Incorrect behaviour
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None

    _______________________________________________________

Details:

Consider a 2x2 EPS file.  A simple example containing only a dot--call it
"dot.eps"--would be:

%!PS-Adobe-3.0 EPSF-3.0
%%BoundingBox: 0 0 2 2
/Times-Roman findfont 8 scalefont setfont 0 0 moveto
(.) show

Take a groff file that puts three lines at the bottom of a page: a line of
text, this tiny EPS image (via .PSPIC), and another line of text:

.sp 63
Line 1
.PSPIC -L dot.eps
Line 3

"Line 3" ends up at the very bottom of the page, and no second page is
needed.

Now increase the .sp from 63 to 64.  What this should do is leave the EPS
image at the bottom of the first page, and move "Line 3" to the top of the
second page.

What it does instead is put both the EPS image and "Line 3" at the top of the
second page, despite there being plenty of room for a 2x2 image below "Line 1"
on the first page.

I included "Line 3" for illustration purposes, but this bug is triggered even
if "Line 3" is absent, meaning that the ".sp 64" case generates an unwanted
extra page of output, when all the output should fit on one page.




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?50770>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]