Conference vaxuum::document_ft

    
    KEEP in BL7 is equivalent to NOFLOAT. In fact, NOFLOAT still works.
    You do need to use when the text formatter goes too far in floating
    things...
    
    patti 

    I tried <EXAMPLE_ATTRIBUTES>(KEEP).  The examples no longer float,
    but some (not all) begin on a new page, leaving white space on
    the preceding page -- enough white space for the example to fit
    in easily...
    
    In addition, the description of KEEP in the documentation is rather
    different than what you describe.  The documentation says for KEEP
    "specifies whether the example is to be kept on one page".  The
    old NOFLOAT would leave the example where it appeared in text,
    dividing it at <valid_break> points.  This is what I really want.
    
    

    
    you are correct that the documentation needs to be changed.
    
    can you send me the file? I'd like to look at the page breaks.
    
    patti

    
    Having seen the file both ways (with and without float), it's clear
    that this is an instance in which KEEP (NOFLOAT) should always be
    used: there are sequences of examples with callouts, each example
    followed by a callout list. Since the text is dependent on the
    example and the text following in order, these should all be coded
    NOFLOAT. When they are, the text is fine.
    
    patti anklam

    Yes, KEEP or NOFLOAT keeps the text from floating.  However,
    as I pointed out in 117.2, some examples start a new page,
    leaving the previous page 3/4 blank, even though the example
    would easily fit there.  I have tried both GENERAL and
    SOFTWARE.REFERENCE documents, and both have this problem.
    

    I was having the same trouble with large figures.  I was just *sure*
    they would easily fit on the previous page, but when I pulled out
    my ruler and started doing some measuring I discovered the the bottom
    margin for was farther up on the page than I thought.
    
    My tests with the GENERAL doctype show that measuring 3 picas
    down from the baseline of the last line of text before the figure
    will be approximately where the top of the figure starts (the figure
    title goes in between there).  I assume this would be similar for
    examples.  Mark this as the starting point on the page, and then
    as the end point, measure up 4 picas from the baseline of the footer.
    The example (or figure) must fit between these two points. 
    
    Perhaps this kind of checking has already been done, and there really
    is a bug.  Just wanted to pass along my experience when I got
    frustrated in the same way mentioned in .0,.2, and .5.
    
    -- Craig

    No, these examples are not large.  In one case, the example, including
    caption and white space at the end, is 1-1/2 inches long.  The space
    left on the previous page is about 6-1/2 inches long.  Further along,
    an example 2 inches long starts on a new page, leaving about 8 inches
    of blank page preceding it...

    Any new information on this?
    
    We use GENERAL and will have zillions (well, almost), and they
    are often very small, and cannot float.
    
    I am about to start the next (big) report using the field test
    instead of bl .6, and this has me rather nervous.
    
    	P

    
    it is fixed for the FT update; in any event, if the problem
    occurs with the current (BL7) system, you can work around any
    really unsightly page breaks by doing explicit <final_cleanup>(page_
    break) where necessary.