[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxuum::document_ft

Title:DOCUMENT T1.0
Notice:**New notesfile (DOCUMENT.NOTE) now available (see note 897)**
Moderator:CLOSET::ADLER
Created:Mon Feb 09 1987
Last Modified:Thu Oct 31 1991
Last Successful Update:Fri Jun 06 1997
Number of topics:897
Total number of notes:4397

579.0. "Table problems" by COOKIE::JOHNSTON () Tue Jun 30 1987 20:30

You should know these things about <table>:

1.  GUTENTAG complains about symbol-name, telling me it's not valid when
    <table> is coded thus:

          <table>(The Vegetable Protein Food Group\protein_tbl )

2.  Processing the table shown on page 3-8 in Step-By-Step (the one
    shown in item #1), for MANUAL doctype pushes the information under
    the second column, first table row right next to the  third column:


       Nuts   Almonds, cashews, peanuts45-60 calories/gram
              macadamia nuts, and fil
              -berts



It's my thinking that this kind of output starts to make document 
document-design dependent.  I would have at least expected DOCUMENT to 
switch to the smaller font, as it would have in BL7.

Also, there are many, many errors in the UG1 table of contents (incorrect page 
numbers).


Thanx

Rose
T.RTitleUserPersonal
Name		DateLines
579.1Source file and more infoCOOKIE::JOHNSTONTue Jun 30 1987 20:5927
Methinks that the fact of the matter is that MANUAL is very messy when it 
handles tables.  Here's the sample code from the Step-By-Step:

<TABLE>(Vegetable Protein Food Group\protein_tbl)
<TABLE_SETUP>(3\10\15)
<TABLE_HEADS>(Protein Foods\Examples\Calories Per Gram of Protein)
<TABLE_ROW>(Nuts\Almonds, cashews, peanuts, macadamia nuts, and
filberts\45-60 calories/gram)
<TABLE_ROW>(Seeds\Sunflower, pumpkin, and poppy\30-55 calories/gram)
<TABLE_ROW>(Dried beans\Soldier, navy, kidney, and chick
peas\30-40 calories/gram)
<TABLE_ROW>(Dried peas\Split, whole green, and yellow\25 calories/gram)
<ENDTABLE>


I have fiddled with the table setup, increasing and decreasing column
widths; no matter what I do, the second column in the table runs into
the third column.  All changing the table widths does is affect *which*
row in the second column runs into the third column.

Was MANUAL documented as having problems? Does/did anyone know about this?


Thanx

Rose
579.2Aw nuts!CLOSET::SEGALWed Jul 01 1987 10:597
    Note 337 discusses problems with justified doctypes and hyphenation.
    The problem here is further compounded by the text formatter.
    I checked out how TeX expected peanuts, macadamia, and poppy should
    hyphenate and got back NO known hyphenation points. Nuts.
    Try <hyphenate>(pea\nuts) using the original column settings.
    
    Lee
579.3bold table heads don't work as in U.G. examplesTOPDOC::FRASCINELLAFri Aug 14 1987 15:5619
    I question the accuracy of all the examples for the various <table>
    tags in the VAX DOCUMENT User Manual, Volume 1, August 1987.
    The examples of <table_heads> lead you to believe
    that you get bold table headings by default.  Yet when I used DOCUMENT
    here on TOPDOC (BL8), the headings came out in normal typeface.
    
    It seems like you actually have to emphasize each heading, for example:
    
    <table_heads>(<emphasis>(1st head\bold)\<emphasis>(2nd head\bold)\etc)
    
    That seems awfully messy.
    
    Could anyone tell me where is the problem?  In the manual or in
    the software, or me?
    
    Thanks,
    
    Michael Frascinella
579.4Examples are not indicative of all doctypesCOOKIE::JOHNSTONFri Aug 14 1987 20:5218
The problem is you, but don't lose any sleep over it! |-)

The type of table heads you get are dependent on the doctype.  I haven't
tried all possible doctypes so can't compare one to another for you, but
I know that the soft.spec table heads are bolded; but table heads in overheads
are not bolded because all text in overheads is bolded by default.

If you are manually bolding table heads, I think that you are working against
the product.  If you generally like a particular doctype but want some
modifications here and there, create your personal doctype as described
in the "Designer's Guide". 

Table heads output may or may not be something that you can easily modify; 
you'll have to read the "Designer's Guide" to find out.

Rose