[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

351.0. "Two Questions - bad examp in tutorial, absolute column spec" by MIZPAH::ELKIND (Steve Elkind) Wed May 06 1987 18:37

(This note sort of ties in with 151.9 and 250.*)

In STEP_BY_STEP, the first <Table> example does not work, with line-to-long
errors.  I've just spent an hour or so going through this file looking for
a fix, and to see if someone else noticed.

I see that at least one other person noticed, although no comment was made.
Will the example be fixed before we send the stuff to customers?

Question 1:  I've tried all kinds of combinations of column-width specs, and
   haven't been able to come up with one that does not give me those errors
   and a bogus-looking table.  I've even tried putting an extra column in,
   to no avail.  Has anyone else managed to force this table to work?

Perhaps this belongs in a reply to note 250, but here goes:

Question 2:  Is it possible to allow the user the OPTION of specifying
   absolute column width (e.g., in cm?), as, say, Scribe does?  I found when
   using Scribe that one pass followed by a little work with a ruler usually
   gave me quite acceptable results.  With this example I've mucked around
   with multiple combinations, lots of time for document compiles, and have
   yet to have any luck.

(Scribe TM of Unilogic?)
T.RTitleUserPersonal
Name
DateLines
351.1will checkCLOSET::ANKLAMThu May 07 1987 01:545
    
    Will double-check the step-by-step (we haven't gone to print yet)
    
    Changing the way we specify table margins is on the wish-list.
    
351.2I found a crockMIZPAH::ELKINDSteve ElkindThu May 07 1987 13:4116
In case anyone else is still puzzling it out, I did come up with a crock
that produces a resonable output from the table example in "Step by Step...".
I simply introduced a fourth column between the second and third original
columns to keep the third column from overwriting the second.  I still
get the "line too long" error, but at least the output looks good:

<table>(The Protein Food Group\protein_tab)
<table_setup>(4\10\25\5)
<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>
351.3Need to know the version of the book.VAXUUM::CORMANThu May 07 1987 17:335
    Can you tell me the date on the Step-By-Step copy you have? Also,
    could you tell me the exact page of that table example? I am fairly
    sure that the table example was fixed for the latest release, but
    want to triple check.
    Thanks. Barbara
351.4sure thing..MIZPAH::ELKINDSteve ElkindFri May 08 1987 09:1425
Sure thing.....

The manual is dated Nov, 1986.  The file, which I got from 
CLOSET::USE3$:[SDML.BL7] as per the instructions on how to get T1.0, is dated
18-Nov-86.

The first appearance of the table example is on page 3-6.

The problems with it are:
    1.  "line too long" messages
    2.  The third column in the first row overwrites the tail end of the
        second column
    3.  There is lots of white space to the right of the third column; the
        table looks off-center

In doing a directory of CLOSET::USE3$:[SDML...]STEP*.*, I found a version
of STEP_BY_STEP_WRITING.LN3 dated yesterday in [.BL8], and also found 
in [.BL7] a STEP_BY_STEP_WRITING.LNO that was dated January.
    1.  Is it correct to assume the one in [.BL8] is some working version,
        and I should "keepa-my-hands-off"?
    2.  Are the [.BL7]STEP*.LNO files, with later dates, more up-to-date than
        the .LN3 versions?  I have no way of telling, as I have no access to
	an LN01.

Thanks for your help (and, of course, for such a nice product!)
351.5Those little errors do slide by, sometimes.VAXUUM::CORMANFri May 08 1987 12:5219
    OK, I'm checking it out. I have a bad feeling that the fix slipped
    through the cracks for the version that you saw in USE3$:[SDML.BL8],
    which was an updated version for Field Test Update. Basically, the
    fix to this error is to add alittle more space to the columns
    (that is, right now the <table_setup> tag has arguments of (3\10\15),
    but it needs something like (3\15\20). I'm not quite sure of the
    numbers, need to experiment alittle.)
    
    The files you noticed in [SDML.BL8] are available for anyone, to
    go along with the Baselevel 8 software (to be released on Monday
    or Tuesday of next week, I understand, when VAXUUM is alive and
    kicking again). If you want to print out a copy before you have
    BL8 installed, feel free. I also don't know how new those [SDML.BL7]
    LNO files are, so you probably should just copy the latest LN03
    file.
    
    -Barbara
    
    -Barbara
351.6Software bug, not documentationBOOKIE::GENTParty gone out of bounds -- B52&#039;sSat May 09 1987 18:0911
    Whoa! Barbara, I think you're missing the point. Certainly, you
    can work "around" the problem by fiddling the numbers. However,
    that only hides the problem, it doesn't solve it. 
    
    The problem is that the software shouldn't be overwriting the
    columns in the first place (since there is room to rearrange 
    the words).  In fact, depending on the size of the increase,
    changing the column width can aggrevate the problem because
    DOCUMENT moves another word onto the first line.
    
    --Andrew
351.7ref #337 alsoCLOSET::ANKLAMMon May 11 1987 19:005
    
    Yes, this appears to be the same issue as in #337. I will be looking
    at this.
    
    patti