|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This page gives you information about syntax to build wiki-tables in MediaWiki. Spreadsheet to wiki table formatTo convert from spreadsheets such as Gnumeric, MS Excel or OpenOffice.org Calc, go here. Using the toolbarYou can use the Mediawiki edit toolbar to create tables on wikipedia, and some wikimedia projects. It is helpful to generate the necessary codings. However on many MediaWiki wikis (and by default) the table tool is not available. To Do: Link to enable Tables on MediaWikis. Use the first button on the right of the toolbar to insert a table when editing a page. By default, it includes the following text:
{| class="wikitable"
|-
! header 1
! header 2
! header 3
|-
| row 1, cell 1
| row 1, cell 2
| row 1, cell 3
|-
| row 2, cell 1
| row 2, cell 2
| row 2, cell 3
|}
Pipe syntax tutorial
Although HTML table syntax also works, special wikicode can be used as a shortcut to create a table. The pipe (vertical bar) codes function exactly the same as HTML table markup, so a knowledge of HTML table code will help in understanding pipe code. The shortcuts are as follows:
{| table code goes here |}
{|
|+ caption
table code goes here
|}
{|
|+ The table's caption
|-
cell code goes here
|-
cell code goes here
|}
{|
|+ The table's caption
|-
| cell codes go here
|-
| cells in the next row go here
| more cells in the same row here
|}
{|
|+ The table's caption
|-
|Cell 1 || Cell 2 || Cell 3
|-
|Cell A
|Cell B
|Cell C
|}
{| border="1"
|-
|format modifier (not displayed)|These all |(including the pipes)|go into |the first cell
|-
|}
which is probably not what you want:
However, the format modifier is useful:
{| border="1"
|-
|Cell 1 (no modifier - not aligned)
|-
|align="right" |Cell 2 (right aligned)
|-
|}
Just remember: no more than 2 single pipes on a line!
{|
|+ The table's caption
! Column heading 1 !! Column heading 2 !! Column heading 3
|-
|Cell 1 || Cell 2 || Cell 3
|-
|Cell A
|Cell B
|Cell C
|}
{|
|+ The table's caption
! Column heading 1 !! Column heading 2 !! Column heading 3
|-
! Row heading 1
| Cell 2 || Cell 3
|-
! Row heading A
|Cell B
|Cell C
|}
{| border="1"
|+ The table's caption
! Column heading 1 !! Column heading 2 !! Column heading 3
|-
! Row heading 1
| Cell 2 || Cell 3
|-
! Row heading A
|Cell B
|Cell C
|}
The final table would display like this:
The table parameters and cell parameters are the same as in HTML, see [1] and Table (HTML). However, the A table can be useful even if none of the cells have content. For example, the background colors of cells can be changed with cell parameters, making the table into a diagram, like m:Template talk:Square 8x8 pentomino example. An "image" in the form of a table is much more convenient to edit than an uploaded image. Each row must have the same number of cells as the other rows, so that the number of columns in the table remains consistent. For empty cells, use the non-breaking space With colspan and rowspan cells can span several columns or rows, see the Mélange example below. However, this has the disadvantage that sorting does not work properly anymore. ExamplesSimple exampleBoth of these generate the same output. Choose a style based on the number of cells in each row and the total text inside each cell. Wiki markup
What it looks like in your browser
Multiplication tableWiki markup
What it looks like in your browser (see: Help:User_style)
Color; scope of parametersTwo ways of specifying color of text and background for a single cell are as follows. The first form is preferred: Wiki markup
What it looks like in your browser
Like other parameters, colors can also be specified for a whole row or the whole table; parameters for a row override the value for the table, and those for a cell override those for a row: Wiki markup
What it looks like in your browser
To make the table blend in with the background, use See : style, background, list of colors, web colors Width, heightThe width and height of the whole table can be specified, as well as the height of a row. To specify the width of a column one can specify the width of an arbitrary cell in it. If the width is not specified for all columns, and/or the height is not specified for all rows, then there is some ambiguity, and the result depends on the browser. Wiki markup
What it looks like in your browser
Note that Setting your column widthsIf you wish to force column widths to your own requirements, rather than accepting the width of the widest text element in a column's cells, then follow this example. Note that wrap-around of text is forced.
To set column widths in a table without headers, specify the width in the first cell for each column, like this:
One application of setting the widths is aligning columns of consecutive tables:
Vertical alignmentBy default data in tables is vertically centrally aligned, which results in odd-looking layouts like this:
To fix this, apply the valign="top" attribute to the rows (unfortunately it seems to be necessary to apply this individually to every single row). For example:
PositioningOne can position the table itself, and all contents in a row, and contents in a cell, but not with a single parameter for all contents in the table, see m:Template talk:Table demo. Do not, under any circumstances, use "float" to position a table. It will break page rendering at large font sizes. MélangeHere's a more advanced example, showing some more options available for making up tables. Note however that with colspan and rowspan sorting does not work properly anymore. You can play with these settings in your own table to see what effect they have. Not all of these techniques may be appropriate in all cases; just because you can add colored backgrounds, for example, doesn't mean it's always a good idea. Try to keep the markup in your tables relatively simple -- remember, other people are going to be editing the article too! This example should give you an idea of what is possible, though. Wiki markup
What it looks like in your browser
Floating tableWiki markup
What it looks like in your browser
Nested tablesFive different (blue) tables are shown nested inside the cells of a table. Automatically the two tables |A| and |B|B| are vertically aligned instead of the usual side by side of text characters in a cell. "float" is used to fix each of tables |C| and |D| to their own position within one cell of the table. This may be used for charts and schemes. Nested tables must start on a new line. Wiki markup
What it looks like in your browser
Combined use of COLSPAN and ROWSPANWiki markup
What it looks like in your browser
Note that using Centering tablesCentered tables can be achieved, but they will not "float"; that is to say, no text will appear to either side. The trick is {| style="margin: 1em auto 1em auto" Wiki markup
What it looks like in your browser
Setting parametersAt the start of a cell, add your parameter followed by a single pipe. For example width="300"| will set that cell to a width of 300 pixels. To set more than one parameter, leave a space between each one. Wiki markup
What it looks like in your browser
Decimal point alignmentA method to get columns of numbers aligned at the decimal point is as follows: Wiki markup
What it looks like in your browser
If the column of numbers appears in a table with cell padding or cell spacing, one can still align the decimal points without an unsightly gap in the middle. Embed a table in each number's cell and specify its column widths. Make the embedded tables' column widths the same for each cell in the column. (If decimal points are still misaligned using this method, the main table's column may be too narrow. Add a parameter to increase the column's width.) Wiki markup
What it looks like in your browser
In simple cases one can dispense with the table feature and simply start the lines with a space, and put spaces to position the numbers: 432.1 43.21 4.321 Style classes
In the first line of table code, after the "{|", instead of specifying a style directly one can also specify a CSS class. The style for this class can be specified in various ways:
Instead of remembering table parameters, you just include an appropriate style class after the
simply by replacing inline CSS for the table by Wiki markup
What it looks like in your browser
Notice that the table retains the gray background of the wikitable class, and the headers are still bold and centered. But now the text formatting has been overridden by the local style statement; all of the text in the table has been made italic and 120% normal size, and the wikitable border has been replaced by the red dashed border. Of course this works only for browsers supporting inline CSS, if it's important use XHTML markup like SortingTables can be made sortable by adding
A long form of abbreviated content can be put as legend outside the table. Wiki markup
What it looks like in your browser
Row templateRegardless of whether wikitable format or HTML is used, the wikitext of the rows within a table, and sometimes even within a collection of tables, has much in common, e.g.:
In that case it can be useful to create a template that produces the syntax for a table row, with the data as parameters. This can have many advantages:
Example: Using m:help:table/example row template (talk, backlinks, )
{| class="wikitable sortable"
|-
! a
! b
! a/b
{{help:table/example row template| 50|200}}
{{help:table/example row template| 8| 11}}
{{help:table/example row template|1000| 81}}
|}
gives:
Conditional table rowFor a conditional row in a table, we can have:
{| class=wikitable
{{ #if:1|{{!}}- <!-- Row one will be shown because the '1' evaluates to TRUE -->
! row one, column one
{{!}}row one, column two}} <!-- {{!}}'s get evaluated to the pipe character '|', i.e. template:! just contains '|' -->
{{ #if: |{{!}}- <!-- Row two NOT shown because the space between the ':' and the '|' evaluates to FALSE -->
! row two, column one
{{!}}row two, column two}}
|- <!-- Row three will be shown -->
! row three, column one
| row three, column two
|}
Which gives the following table: (note how the second row is missing)
Other table syntaxOther types of table syntax that MediaWiki supports:
All three are supported by MediaWiki and create (currently) valid HTML output, but the pipe syntax is the simplest. Also, HTML & wiki-<td> syntax (i.e., unclosed <td> and <tr> tags) will not necessarily remain browser-supported in the upcoming future, especially on handheld internet-accessible devices. See also Table (HTML), HTML element#Tables. Note however that the Comparison of table syntax
See also Template talk:For#Tables. Pipe syntax in terms of the HTML producedThe pipe syntax, developed by Magnus Manske, substitutes pipes (|) for HTML. There is an on-line script which converts html tables to pipe syntax tables. The pipes must start at the beginning of a new line, except when separating parameters from content or when using TablesA table is defined by {| ''params'' |} which equals <table ''params''>Insert non-formatted text here </table> Rows<tr> tags will be generated automatically for the first row. To start a new row, use |- which results in <tr> Parameters can be added like this: |- params which results in <tr params> Note:
CellsCells are generated either like this: |cell1 |cell2 |cell3 or like this: |cell1||cell2||cell3 which both equal <td>cell1</td><td>cell2</td><td>cell3</td> so "||" equals "newline" + "|" Parameters in cells can be used like this: |params|cell1||params|cell2||params|cell3 which will result in <td params>cell1</td> <td params>cell2</td> <td params>cell3</td> HeadersFunctions the same way as TD, except "!" is used instead of the opening "|". "!!" can be used instead of "||". Parameters still use "|", though! Example: !params|cell1 CaptionsA <caption> tag is created by |+ Caption which generates <caption>Caption</caption> You can also use parameters: |+ params|Caption which will generate <caption params>Caption</caption> Displaying the table code which generates a tableThe code for a simple wiki markup table inside a Code box can be seen below.
{| border="5" cellspacing="5" cellpadding="2"
| style="text-align: center;" | [[Image:gnome-system.png]]
|-
! Computer
|-
| Processor Speed: 1.8 GHz
|}
Above code produces/displays the table below:
Below code, generated and displayed the above table's Code box code itself, on the screen and web page, inside a blue colored dashed bordered rectangular box.
Note that, HTML tag <pre> was used to achieve displaying the above codes and the Code box. Other alternatives to display table codeIn most cases, when a code line is longer than the web browser window's width, then a scrolling bar appears at bottom, to let the viewer slide to the right side (and also left side) to see the rest of the codes, because, the use of <pre> tag causes the code line to remain intact, unless an EOL (CR/LF) hidden character is reached in that text line. But having to slide or scroll to the right or left for viewing the full codes is often not comfortable to many readers. To solve such problem, using the <p>, <tt> and <br /> HTML tags, are better than using the <pre> tag, as those will limit the length of a line of code according the available space in the web browser's window and therefor will not result in the need to move the scroll-bar right (or left) for viewing. By placing the codes inside the <tt>...</tt> HTML tags, codes are displayed with a fixed width text/font, (like the <pre> tag uses) for easier reading. HTML tag <br /> is used to display (or bring) next line of codes, starting from the next line. HTML tag <p> along with its CSS style properties, is used to create the blue colored dashed bordered rectangular box (Code box) around the codes, (like the HTML <pre> tag, which gets these properties from the main.css stylesheet file). An example of table code with a long line is: {| border="5" cellspacing="5" cellpadding="2" producing the below table:
Code box above the table has the auto line wrapping feature enabled. Note the long line (the sixth line from top) inside the codes, which is wrapped inside the Code box. This Code box and the codes, can be displayed by using below codes in the edit box. <p style="padding: 1em; border: 1px dashed #2f6fab; color: Black; background-color: #f9f9f9; line-height: 1.1em;"> <tt> See the above codes, note that, <nowiki>...</nowiki> tags were used to disable wiki markup codes for beginning a table ({|), ending a table (|}), start of an image displaying ([), or a hyperlink, etc. All wiki & HTML markup codes need to be disabled by enclosing them inside the <nowiki>...</nowiki> tags. If these codes were to be displayed inside another table, then, each | (pipe) & ! (Exclamation mark) symbol also needed to be enclosed inside the <nowiki> tags. Note that, the longer line is automatically wrapped according to the width of the web browser's window, inside the Code box. Alternatively, we can replace each | (pipe symbol) character with | (HTML decimal entity code), replace each ! (exclamation mark) with ! code, replace { (beginning curly/second bracket) with { and we may replace } (closing curly/second bracket) with } code. Also replace the < (less than sign, or beginning angle bracket) with < numeric entity code or, replace it with < (HTML symbol entity code). For more on HTML decimal or hexadecimal numeric entity codes, please see w:Windows Alt codes. To display the wiki image markup code, we should replace the (beginning square/third bracket) with [ and we may replace (closing square/third bracket) with ]. When we are replacing characters with their numeric enitity codes, we are actually disabling their normal functionality, so we can display them on the web page(s). <p style="padding: 1em; border: 1px dashed #2f6fab; color: Black; background-color: #f9f9f9; line-height: 1.1em;"> <tt> See also disabling wikitext interpretation and/or reformatting. Square monitorsTo format for a square monitor or window, use a tape measure. Determine the height of your rectangular screen. Using that figure measure under the screen to determine the width your monitor’s screen would be if it were square. Mark that location using ink or tape under the screen. Drag the side of your browser’s window to that location so the window is square based on accurate measurements. Square monitors and reading windows are not able to contain tables and galleries made for rectangular and wide screens. When a table or gallery is wider than the monitor, it makes every line of text wider than the screen as well. The px amounts of the following gallery were determined after measuring the window to make sure it was square: Type this:
Wikipedia-specific help
Wikitable as image galleryA wikitable can be used to display side-by-side images, in the manner of an image gallery (formatted by "<gallery>"), but with larger images and less vacant area around photos. A simple framed gallery can be formatted using class="wikitable" to generate the minimal thin-lines around images/photos within the table:
{| class="wikitable"
|-
|<!--column1-->[[Image:Worms 01.jpg|265px]]
|<!--column2-->[[Image:Worms Wappen 2005-05-27.jpg|235px]]
|-
|<!--column1-->Nibelungen Bridge to Worms<br/>across the [[Rhine]]
|<!--column2-->Worms and its sister cities
|}<!--end wikitable-->
Note the result below (with thin-lined cells):
Another issue about the standard "<gallery>" tag, in 2007, was that it put 4 images per line, overrunning the right margin of a wiki article, unless the gallery was stopped at 3 images. However, a wikitable uses typical image-links with sizes, such as "[[Image:XXX.jpg|130px]]" so 4 images could be displayed on a wikitable line within a 600px width (for 800x600 resolution screens).
{| class="wikitable"
|-
|<!--col1-->[[Image:Worms 01.jpg|130px]]
|<!--col2-->[[Image:Worms Wappen 2005-05-27.jpg|125px]]
|<!--col3-->[[Image:Liberty-statue-with-manhattan.jpg|125px]]
|<!--col4-->[[Image:New-York-Jan2005.jpg|125px]]
|-
|<!--col1-->Nibelungen Bridge to Worms
|<!--col2-->Worms and its sister cities
|<!--col3-->Statue of Liberty
|<!--col4-->New York City
|}<!--end wikitable-->
Another advantage about wikitable images, compared to "<gallery>" formatting, is the ability to "square" each image when similar heights are needed, so consider putting 2-number image sizes (such as "199x95px"), where the 2nd number limits height:
{| class=wikitable
|-
|<!--col1-->[[Image:Liberty-statue-with-manhattan.jpg|199x95px]]
|<!--col2-->[[Image:New-York-Jan2005.jpg|199x95px]]
|<!--col3-->[[Image:Gold star on blue.gif|199x95px]]
|<!--col4-->[[Image:Worms 01.jpg|100x95px]]<!--smaller-->
|-
|<!--col1-->Statue of Liberty
|<!--col2-->New York City
|<!--col3-->Star on blue
|<!--col4-->Bridge to Worms
|}<!--end wikitable-->
Note the 3 images sized "199x95px" appear identical height, of 95px (4th image purposely smaller). The "95px" forces height, while "199x" fits the various widths (could even be "999x"):
Therefore, the use of size "199x95px" (or "999x95px") produces the auto-height-sizing beyond the "<gallery>" tag, and with the option to set taller thumbnails ("199x105px"), or even to have some images purposely smaller than other images of "95px" height. A very short height ("70px") allows many more images across the table:
{| class=wikitable
|-
|<!--col1-->[[Image:Liberty-statue-with-manhattan.jpg|199x70px]]
|<!--col2-->[[Image:Gold star on blue.gif|199x70px]]
|<!--col3-->[[Image:New-York-Jan2005.jpg|199x70px]]
|<!--col4-->[[Image:Gold star on deep red.gif|199x70px]]
|<!--col5-->[[Image:Worms 01.jpg|199x70px]]<!--same height-->
|<!--col6-->[[Image:Gold star on blue.gif|199x70px]]
|}
The above wikitable-coding produces the result below, of 6 columns:
Once images have been placed in a wikitable, control of formatting can be adjusted when more images are added. Shifting/centeringImages within a wikitable can be shifted by inserting non-breaking spaces (" ") before or after the image-link (" [[Image:]]"). However, auto-centering simply requires use of center-tags to be placed around an image-link for centering in a cell ("<center>[[Image:..]]</center>"). In the example below, note how Col2 uses <center>, but Col3 uses " ":
{| class=wikitable
|-
|<!--Col1-->[[Image:Domtoren_vanaf_Brigittenstraat.jpg|299x125px]]
|<!--Col2--><center>[[Image:Utrecht 003.jpg|299x125px]]</center>
|<!--Col3--> [[Image:Uitzicht--Domtoren.jpg|299x125px]]
|-
|<!--Col1-->Dom tower from Brigittenstraat
|<!--Col2-->Cloister garth of the Utrecht Dom Church
|<!--Col3--> <small>View from bell tower</small>
|}
The above coding generates the table below: note the middle garden image is centered (but not the left image), and the right image has 2 spaces before " View...":
Also note that tag "<small>" made a smaller text-size caption. Speed/transfer ratesSometimes, the larger wikitable images are much faster (3x-8x faster) than formatting the smaller <gallery> images, contrary to the notion that "smaller images should use less data" (not always true). It is not easy to predict why wikitables (with larger images) are so much faster: perhaps older gallery images were thumbnailed as larger data-blocks, but when reformatted as larger images for a wikitable, the new (larger) thumbnails become 3x-8x more streamlined, so 3x-8x faster in data transfer than <gallery> images. However, actual transfer/display speeds depend on the individual files. In October 2007, PNG-format files often stored as 5%-10% slightly smaller than equivalent GIF files, but upon wiki-thumbnailing, the PNG files were converted to massive high-resolution form, where a PNG-format image became a gargantuan data file, often 9x-21x times heavier (more data) than a similar JPEG thumbnail. However, even the quick JPEG photo images might become another 3x-8x faster in a wikitable, rather than as <gallery> images.
Transfer display speeds are difficult to predict, so beware standardizing any image format as better or "faster" than another. Whereas a trimmed, full-size PNG file might display 10% faster than a full-size GIF file, the thumbnailed PNG was typically 4x slower than GIF thumbnails, while PNG was 9x-21x times slower than JPEG thumbnails. The most important issue is that wikitable-images can be larger, clearer than <gallery> images, more important than some wikitable images being 3x-8x faster than the smaller gallery images.
This page is a copy of the master help page at Meta (for general help information all Wikimedia projects can use), with two Wikipedia-specific templates inserted. To update the main text, edit the master help page for all projects at m:Help:Table. For Wikipedia-specific issues, use Template:Ph:Table (the extra text at the bottom of this page) or Template:Phh:Table for a Wikipedia-specific lead (text appears at the top of this page). You are welcome to replace the full wikitext of this page with that of the master page at Meta at any time. To view this page in other languages see the master page at Meta. See also
External links
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| All Right Reserved © 2007, Designed by Stylish Blog. |