| 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 |
Based on the example on page 13-216 of the User's Guide, Part 1,
I created the following table. However, using the GENERAL doctype
and LN03 destination, I keep getting a page break after the line
containing the spanning head "Schedule". The only difference I
can see between this and the book example is the additional two
lines of spanning heads I've included. Is there some limit to the
number of successivle <TABLE_HEADS> lines before the page break
gets inserted?
Thanks.
-pd
<TABLE>(Project Status)
<TABLE_SETUP>(3\40\10)
<TABLE_HEADS>(<SPAN>(3\LEFT)Project: )
<TABLE_HEADS>(<SPAN>(3\LEFT)Project Leader: Peter Davis<RULE>)
<TABLE_HEADS>(\<SPAN>(2)Schedule)
<TABLE_HEADS>(Milestones\Original\Revised<LITERAL>(/)Actual)
<TABLE_UNIT>
<TABLE_UNIT_HEADS>(<SPAN>(3\LEFT)Accomplishments last month:)
<TABLE_ROW>(\\)
<ENDTABLE_UNIT>
<TABLE_UNIT>
<TABLE_UNIT_HEADS>(<SPAN>(3\LEFT)Plans for next month:)
<TABLE_ROW>(\\)
<ENDTABLE_UNIT>
<ENDTABLE>
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 268.1 | <literal>(/) unnecessary | VAXUUM::KOHLBRENNER | Mon Apr 20 1987 15:28 | 13 | |
I can't answer your problem with the page break, but I see
that you are making a literal out of an ordinary "slash"
character. The tag translator doesn't give the slash (/)
any meaning, so there should never be a need to make a
literal out of it.
It is easy to confuse a slash and a backslash, however, both
in the typing and in reviewing what you have typed. And since
the <table_row> tag does not complain if you give too few or
too many arguments, I suppose it might be a good habit to
draw attention to regular slashes by making them literals.
In any case, it is a matter of style not of necessity.
| |||||
| 268.2 | need to see the file | CLOSET::ANKLAM | Tue Apr 21 1987 09:09 | 5 | |
I don't know about the table breaking, either. I would like to see
the file to see if I can duplicate the error.
| |||||
| 268.3 | PDVAX::P_DAVIS | aka SARAH::P_DAVIS | Tue Apr 21 1987 11:27 | 12 | |
Re/ .1:
I had thought that "/" and "\" were both treated as separators in
an argument list. That's why I used <LITERAL>. The page break
occurs before that point, however.
Re/ .2:
The whole table's in .0. That should be enough to reproduce the
problem, since that's all there was when I found it.
-pd
| |||||
| 268.4 | can't duplicate | CLOSET::ANKLAM | Tue May 26 1987 12:22 | 10 | |
Peter,
I really have had an awful time duplicating this problem with the
table as is in .0 ... the table macros just aren't supposed to allow
breaks between table headings. If there were a stray index tag
or <p> tag between <table_head> tags, that would explain the break.
-patti
| |||||