Convex Press Web

Structuring Documents with FrameBuilder


Previous Page | Next Page | Contents | Convex Press Home | Help

Tips and other flashes of inspiration


Tables

Date of last verification: June 20, 1995

Tables present some interesting issues online. First, make sure your tables follow the requirements listed in the "Do I need to use mifmucker?" section.

Bold headings

The first row of a table must be a heading row to appear bold online. If the first row is a body row, add a heading row as described in the Frame documentation. Cut (removing the table cells) the original first row and paste it (replacing the current row) in the newly added heading row.

Footnotes

Table footnotes are wrapped in <Footnote> elements.

Hidden and visible tables

All visible tables must be titled. Visible tables must be wrapped in <Table> => <All> to display all cell borders.

All hidden tables must be wrapped in <Table> => <None> to be hidden online and to not be counted in PinPoint's list of tables.

Currently, an online table shows all of its cell borders or none of them--there is no selective border display.

Line breaks in table cells

Maintaining line breaks in table cells online is not an easy task--there are no hard and fast rules. The examples below have been know to work, as well as fail. The failures may be due to the width of the cell in Frame.

Having said that, here are some criteria the cell contents must meet if the suggestions below are going to be followed:

Pick one of the following two options depending on your desired formatting:

Assume the table cell contains palatino text and line breaks that you want preserved as in this table.

You could wrap it as follows:

<TableContents> => <ExampleBlock> =><ExampleSegment>

This is line one SHIFT-RETURN

This is line two SHIFT-RETURN

This is line three

</ExampleSegment></ExampleBlock></TableContents>

Now assume the table cell contains monospace text and line breaks that you want preserved, as in the following table.

You could wrap it as follows:

<TableContents> => <ExampleBlockVerbatim>

This is line one SHIFT-RETURN

This is line two SHIFT-RETURN

This is line three

</ExampleBlockVerbatim></TableContents>

These solutions, which may or may not work, depend on using verbatim justification in the style sheet for table elements. Verbatim justification means that the line breaks are preserved just as you see them on the screen. Since visible line breaks may be different depending on whether or not display of element boundaries is turned on, be sure element display is always turned off when you export your document.

Table cells that contain just a single paragraph do not need to be structured at all. Word wrap in these cells will be normal-- that is, the para will be left justified.

See the "Multiple paragraphs in a single cell" section for a related discussion.

Multiple paragraphs in a single cell

Currently, a single table cell cannot contain more than one paragraph, with each paragraph varying with window sizes of PinPoint.

Two or more paragraphs in one cell are treated as a single paragraph--there will be no break between them.

Peter is currently working with the idea of using bullet lists in table cells in order to provide multiple paragraphs in a single cell. Each paragraph will be an item in the list. The bullets will not be present.

Straddling

Straddling table cells does not work online. Avoid this construct.

The table continuation variable

Date of last verification: June 20, 1995

The table continuation variables sometimes add the string (Continued) to the beginning of table titles in PinPoint. The altered titles can be seen in the TOC view (when it is set to List of tables) and in the Main view itself.

If your tables show these title changes, complete the following procedure immediately before exporting to SGML:

  1. Save your document.
  2. Change all the variables to text strings.
  3. Export to SGML.
  4. Revert to the last saved version of your file.

Previous Page | Next Page | Contents | Convex Press Home | Help

Please submit comments and questions about these pages to scox@convex.com