Conference vaxuum::document_ft

347.0. "Overprints on LN03 on TABLE_ROW?" by CSC32::K_WROBEL (Those who can, do ... - CSC/CS Employee Training) Wed May 06 1987 12:35

I checked other notes and didn't see this, so forgive me if this has 
already been noted.

The enclosed table definition creates problems when output on LN03.  The 
word 'database' actually overprints on top of the next col.  (easy to see
visually and hard to describe).  The output is not overprint if output type 
is TERMINAL or MAIL (and, I didn't check other doc types, sorry).

command used is

$DOCUMENT file.GNC GENERAL LN03

<table>
<table_setup>(2\8)
<table_heads>(Component\Description)

<table_row>(Source database\A single, centralized database that provides 
data and data definitions for extractions and replications)

<table_row>(Target Database\A copy of subset of a source database.  A 
target database can be an extraction or replication)

<table_row>(Transfer database\The storage location of all transfer and 
schedule definitions on a single node system or in a VAXcluster)

<endtable>

<table_setup>(2\12)

    
    is this more of 337?
    
    

Peggy,

I looked at 337 (missed it on the first pass thru).  Sounds like the same 
thing.  However, this is just an excerpt from a larger table.  In the larger 
table, in the first col, all entries were first character uppercase.  But, 
some of the entries were wrapped, some were hyphenated, and some were 
overprinted.  If you want to see the entire table, let me know (I think I 
can pull together enough to reproduce all the above behaviors).  And, yes, 
regarding .1 changing the size "fixed" the overprint problem, I was just 
confused about what I was seeing...

	Kathy

ps.  As a *techie* this is a wonderful product!

    
    yes, I think we'd like to see a file. just MAIL it to me. thanks
    
    patti