Conference vaxuum::online_bookbuilding

351.0. "Paragraphs Butt Up Against Each Other" by ELUDE::GREMBOWICZ () Fri Jun 15 1990 14:51

    
    
    
    In a couple of places in the online version of my book, paragraphs 
    butt up against each other.  In both instances, the paragraphs that 
    butt up against each other are part of a list element and are 
    separated by formal figures in the sdml file and 
    in the  postscript version.  
    
    Here's an example of the offending code:
    
    <LIST>(NUMBERED)
    <LE>
    The coordinator writes a commit record for this transaction to its
    transaction log file. As stated in <REFERENCE>(prepare_sec), at this point the
    transaction is guaranteed to commit.
    <LE>
    The coordinator instructs the local resource managers and the remote
    transaction managers to finish processing the commit phase and to make 
    the transaction permanent. Each remote transaction manager instructs the 
    resource managers on its node to finish processing the commit phase and to make the transaction
    permanent.
    <P>
    <REFERENCE>(execute_commit_fig) shows the coordinator and transaction
    managers initiating the commit phase.
    
    <FIGURE>(Initiating the Commit Phase\execute_commit_fig)
    <FIGURE_ATTRIBUTES>(KEEP)
    <figure_file>(ps\zk-1780a.ps\31.2)
    <figure_file>(bookreader\zk-1780a.decw$bookfig\34.7)
    <ENDFIGURE>
    <P>
    The coordinator returns control of the transaction to the application
    so the application can start another transaction.  However, if the new
    transaction involves a database that has not finished committing the changes,
    Rdb/VMS will not start the new transaction until the database has
    completed committing all changes made during the previous transaction.
    .
    .
    .
    
    
    
    In the BOOKREADER, the last paragraph bumps into the previous
    paragraph:
    
    Figure 2-7 shows the coordinator and transaction 
    managers initiating the commit phase.
>   The coordinator returns control of the transaction to
    the application ...
    
    The > indicates where the two paragraphs butt up against each other.
    There is less space there than there usually is between lines.
    
    
    BTW, we're using V1.2B.
    
    Helen
    
    
                           

    Hmm.  I had that problem with the previous versions, but haven't seen
    it since using V2.0 of Bookreader with V1.2-B of DOCUMENT.  I had to
    put extra <p> tags in the old versions, then strip them all out for
    V2.0 with V1.2-B.  Maybe you'll have to resort to that, unless one of
    the technical folks has a better solution.
    
    
    Susan

    I'll check this out and let you know what I find...
    
    Wayne

    The problem has been fixed for the next release.  It happens when there
    is a formal figure, table, or example coded between the paragraphs. 
    Even though they don't appear on the text 'page' (they're popups), they
    were causing the following paragraph to start too high.  
    
    In the meantime, a possible workaround is to use the <CP> tag instead
    of the <P> tag to start the paragraph following a formal figure, table
    or example.  
    
    Wayne