" causes subsequent text on that line to be treated as preformatted text.

Valid attributes and values are:

• align (left, center or right)
• valign (top, middle or bottom)
• colspan (a positive integer)
• rowspan (a positive integer)
• bgcolor (a color name or hex number)
• width (a positive integer or percent)

(:cellnr (attr..):)

Generates a new cell at the beginning of the next row.
Closes the previous table cell, if any.
In HTML, this creates a "<tr><td attr>" tag, and possibly

• align (left, center or right)
• valign (top, middle or bottom)
• colspan (a positive integer)
• rowspan (a positive integer)
• bgcolor (a color name or hex number)
• width (a positive integer or percent)

</table>

Closes the previous table cell and closes off any table. Generates </td>, </tr>, and

Notes

For the table, cell, and cellnr tags the author can specify any attributes that would be valid in the HTML

Many are likely to ask why we didn't just use the standard HTML table markup (

-> %color=green% Common comment: Surely, the average or naive author would not be writing HTML directly, but using a tool, such as FrontPage, or even MSWord, to generate the HTML. This would be a lot simpler than learning even the simplest PmWiki markups.

-> %color=green% Pm's Response: And once the HTML has been generated and posted, how is someone else going to edit or modify the table if they don't have the original FrontPage or MSWord file used to create it? Remember that we're talking about collaborative authoring. The HTML that those packages generate is among the hardest to read and edit of all!

It's difficult to write the code needed to make PmWiki understand and fix arbitrary table markup, so PmWiki uses the simplified version above. Still, this version is able to handle most table requirements (with the possible exception of nested tables).

And, this is not to say that nested HTML tables are impossible in PmWiki --they just can't be easily created by wiki authors using the default wiki markup. A site administrator can of course create header/footer HTML code and other local customizations that make use of nested tables.

Example 1. A table using table directive markup.

<table border=1 cellpadding=5 cellspacing=0>
<cell> a1
<cell> b1
<cell> c1
<cell> d1
<cellnr> a2
<cell> b2
<cell> c2
<cell> d2
</table>

In HTML, this is the same as

->

<table border='1' cellpadding='5' cellspacing='0'>
  <tr>
    <td>a1</td>
    <td>b1</td>
    <td>c1</td>
    <td>d1</td>
  </tr>
  <tr>
    <td>a2</td>
    <td>b2</td>
    <td>c2</td>
    <td>d2</td>
  </tr>
</table>

Floating Table with bulleted navigation list

What if you wanted to create a nice little table like a table of contents in a page like this? In this example, the table is floating right and contains some links in a bulleted list. This is a nice demonstration of how it's possible to build a little table of contents in the page, which might navigate to other pages just within the same wiki group. Note that having a bulleted list won't work in a ordinary table - it only works inside an table created with table directives such as the example code used here.

<table border=1 width=30% align=right bgcolor=#cccc99 cellspacing=0 >
<cellnr>
'''Navigation Links'''
<cellnr>
*[[Tables]]
*[[Table directives]]
</table>

<table border=1 width=30% align=right bgcolor=#cccc99 cellspacing=0 >
<cellnr colspan=2 align=center>
'''Navigation Links'''
<cellnr align=center>
[[Tables]]
<cell align=center>
[[Table directives]]
</table>

Looking at the markup here, notice that we have used a #cccc99 hex color for the table background. also the <cellnr> markup creates a new row, a new cell and closes the row at the end.

You could take this concept a little further: since you might want each page in the group to contain the same table of contents, you can make ONE table like the above and put it in its own page. Then use an include on any of your pages and bring in the table. The float (align) property will be honored in each page where it's included. Pretty sweet!

%trail% <<|Documentation Index|>>

>>faq<<

Q: Can I define table headers using the table directive markup?
A: No, but you can with Cookbook:AdvancedTableDirectives. See Pm's reply to pending PITS:00535