Conference vaxuum::document_ft

91.0. "Measuring white space for <FIGURE_FILE>??" by COOKIE::JOHNSTON () Wed Mar 11 1987 17:21

I have two sixel files, both built with GRED.  

1.  Both sixel files have 1/4" white space at the top and the bottom.  

2.  Figure 1 begins with a box that contains text, like this:

                  +---------------+
                  | Widget Inputs |
                  +---------------+

    The 1/4" white space appears in final output between the box and
    the DOCUMENT rule that is under the Figure caption.  Expected 
    behavior.


3.  Figure 2 begins with straight text, like this:

                     Control Unit

    The text is pushed up against the rule; the white space is lost.


Any ideas on why this happens?

Also, does document automatically add any white space between the 
beginning and ending figure rules?  It looks like it adds space after 
the figure, but I haven't been able to really figure it out.  We 
specificied the same number of picas in <FIGURE_FILE> that were shown on
the VAXstation.  Final output, rule-to-rule, was greater.

Finally, the documentation does not mention it, but you can specify 
partial picas in <FIGURE_FILE>, such as 36.5.  It's accepted, so I'm 
assuming that it's processed as such.

Thanx

Rose

    
    Are you *sure* the two sixel files have the same amount of
    whitespace at the top? You can check by editing them with EDT or
    EVE and counting the number of hyphens at the top of the files. If
    the sixel that is bumping up against the rule has less hyphens
    (blank lines) just add some in to equal the number you see in the
    first figure.
    
    Also, see note 22.6 for a possible fix you could put in your .GNC
    file. 
    
    				Lance
    
                                     

I looked at the files, and interestingly enough, the picture being
pushed up against the rule had *more* blank lines, or 8 "-".  The
picture with the box only had 5.

I'll look at the note referenced in .1.

Thanx for your response.