# HG changeset patch # User Paul Boddie # Date 1333304338 -7200 # Node ID 761bbc3a4c7ea5ef44ab0f7a8ab5d1f43a2b46b2 # Parent 825a3e78d952e74c8067919c6342de30249a073d Fixed an example; improved the columntypes description. diff -r 825a3e78d952 -r 761bbc3a4c7e pages/HelpOnImprovedTableParser --- a/pages/HelpOnImprovedTableParser Sun Apr 01 01:40:28 2012 +0200 +++ b/pages/HelpOnImprovedTableParser Sun Apr 01 20:18:58 2012 +0200 @@ -69,7 +69,7 @@ {{{#!table Already in column #1 || Now in column #2 - until the next row or the end of the table +until the next row or the end of the table }}} }}}} @@ -239,7 +239,7 @@ Although the lines are not too long, it is somewhat difficult to interpret and edit the text. -Here is how the above table can be written in the improved syntax (with the section markers omitted): +Here is how the above table can be written in the improved syntax: {{{{ {{{#!table @@ -350,7 +350,7 @@ In addition to a more flexible syntax, !ImprovedTableParser also allows the contents of tables to be described so that they can be manipulated and shown according to different sorting or ordering criteria. This is done by adding some directives to the table declaration. headers:: indicates the number of rows which are headers, describing non-sortable data - columntypes:: describes the kind of data in each column along with how the column should be ordered (ascending or descending); the syntax is reminiscent of the Unix `sort` utility; column numbering starts at 0 + columntypes:: describes the kind of data in each column along with how the column data should be ordered (ascending or descending) by default if chosen as a sort column; the syntax is reminiscent of the Unix `sort` utility, but column numbering starts at 0 instead of 1 sortcolumns:: describes the initial sorting or ordering of the table data; the syntax is the same as `columntypes` name:: the HTML `id` attribute or anchor given to the table so that when the ordering is changed, the browser will refresh the page and can jump to the table's position