DocBook to HTML - Tables

FIXME

This template processes a single entry element and generates td elements as needed. It then calls itself on the following entry element, adjusting parameters as necessary. Under certain conditions, this template may not be able to output a td element immediately. In these cases, it makes whatever adjustments are needed and calls itself or db2html.entry.implicit (which, in turn, calls this template again when it's finished).

Three parameters are used to determine whether a td element can be output. The spanstr parameter provides infomation about row spans in effect from entries in previous rows; the colpos parameter specifies which column we would output to if we created a td; and the colnum parameter specifies which column this entry should be in, according to any relevant colspec or spanspec elemets.

There are two conditions that cause this template not to output a td element immediately: if the spanstr parameter does not start with 0:, and if the colpos parameter is less than the colnum parameter.

The spanstr parameter specifies the row spans in effect from entries in previous rows. As this template iterates over the entry elements, it strips off parts of spanstr so that only the parts relevant to the entry are present. If spanstr does not start with 0:, then an entry in a previous row occupies this column position. In this case, that value is removed from spanstr, the colpos parameter is incremented, and db2html.entry is called again. Additionally, since db2html.entry.colnum doesn't consider row spans, the colnum parameter may be incremented as well.

If the colpos parameter is less than the colnum parameter, then the document has skipped entries by explicitly referencing a column. This is allowed in CALS tables, but not in HTML. To fill the blank spaces, we call db2html.entry.implicit, which outputs an empty td element spanning as many columns as necessary to fill in the blanks. The db2html.entry.implicit template then calls this template again with appropriate parameter values.

When this template is finally able to output a td element, it calculates appropriate values for the style and class attribute based on DocBook attributes on the entry, the relevant colspec or spanspec, and any relevant ancestor elements. It then calls itself on the following entry element to output the next td.

CALS tables in DocBook don't need to have entry elements for each column in each row, even when the column is not covered by a row-spanning entry from a previous row. An entry can explicitly specify which column it's in, and any previous unfilled columns are considered blank. Since HTML tables don't have this mechanism, we have to insert blank td elements to fill the gaps.

When db2html.entry detects a blank entry, it will call this template with the approprite parameters. This template then calls itself recursively, each time adjusting the colpos, colspan, and spanstr parameters, until it comes across the last column that needs to be filled. It then outputs a td element with an appropriate colspan attribute.

Finally, this template calls db2html.entry again on entry. With the values of colpos and spanstr suitably adjusted, that template is then able to output the td for the entry element.

FIXME

FIXME

This template calculates how many columns an entry element should span. In CALS tables, column spanning is done by specifying starting and ending colspec elements, or by specifying a spanspec element which specifies starting and ending colspec elements.