Search results
Results from the WOW.Com Content Network
For years in HTML, a table has always forced an implicit line-wrap (or line-break). So, to keep a table within a line, the workaround is to put the whole line into a table, then embed a table within a table, using the outer table to force the whole line to stay together. Consider the following examples: Wikicode (showing table forces line-break)
See the Width section of Help:Table. To summarize, max-width is the preferred way to limit widths on tables. It works on divs too. Note though that in both tables and divs there needs to be spaces in long lines of text or wikitext. Otherwise there is no point at which that line can wrap.
{| table code goes here |} An optional table caption is included with a line starting with a vertical bar and plus sign "|+" and the caption after it: {| |+ caption table code goes here |} To start a new table row, type a vertical bar and a hyphen on its own line: "|-". The codes for the cells in that row start on the next line.
Tables will show the "[hide]" / "[show]" controls in the first row of the table (whether or not it is a header row), unless a table caption is present.(see § Tables with captions) Example with a header row
You can add a table using HTML rather than wiki markup, as described at HTML element#Tables. However, HTML tables are discouraged because wikitables are easier to customize and maintain, as described at manual of style on tables. Also, note that the <thead>, <tbody>, <tfoot>, <colgroup>, and <col> elements are not supported in wikitext.
Get AOL Mail for FREE! Manage your email like never before with travel, photo & document views. Personalize your inbox with themes & tabs. You've Got Mail!
PER Aligned: a fixed number of bits if the integer type has a finite range and the size of the range is less than 65536; a variable number of octets otherwise; OER: 1, 2, or 4 octets (either signed or unsigned) if the integer type has a finite range that fits in that number of octets; a variable number of octets otherwise
The wikitext must be correct. An incorrect rowspan organization can break sorting, cause weird table formatting, move data to the wrong column, etc. See examples below. When sorted all the rows are filled. Tables without rowspan are much easier to maintain by less experienced editors, and by editors who are stopping by only once to edit the table.