跳转至: 导航搜索

表格是以行和列呈現數據或信息的方法。 They can be useful for a variety of content presentations on Wikipedia, but should be used only when appropriate; sometimes the information in a table may be better presented as prose paragraphs or as an embedded list.

Avoid referring to tables as being located on the left or right of a display page. Placement is different for viewers of the mobile versions of Wikipedia, and is meaningless to people having pages read to them by assistive software. Instead, use captions to identify tables.


It is recommended that wikitables be used in place of HTML tables, as they are easier to customize and maintain. A standard "wikitable style" is also available, by adding class="wikitable" to the top row of the table. The powerful and useful sorting feature can be enabled by adding class="sortable" to the top row. Extreme caution should be applied if rowspan or colspan is used. It is also possible to combine class, as in class="wikitable sortable".


Table captions and column/row headings should be succinct and self-explanatory. In most cases, individual words or sentence fragments should be used, and articles (a, an, the) are unnecessary. Only the first word in the caption or heading should be capitalized (except for proper nouns), in keeping with Wikipedia's conventions for capital letters. In some rare cases, judicious use of soft hyphens may be helpful; see MOS:HYPHEN for details.


In general, styles for tables and other block-level elements should be set using CSS classes, not with inline style attributes. This is because the site-wide CSS is more carefully tested to ensure compatibility with a wide range of browsers; it also creates a greater degree of professionalism by ensuring a consistent appearance between articles. Deviations from standard conventions are acceptable where they create a semantic distinction (for instance, the infoboxes and navigational templates relating to The Simpsons use a yellow color-scheme instead of the customary mauve, to tie in with the dominant color in the series) but should not be used gratuitously.

See WP:Deviations and Wikipedia talk:Consensus/RfC for guidance on use of coloring or non-standard formatting, and for when MoS and WikiProjects guidance is at variance.

Consideration may be given to collapsing tables which consolidate information covered in the prose.


Screen readers and other web browsing tools make use of specific table tags to help users navigate the data contained within tables. Use the correct wikitable pipe syntax to take advantage of all the features available.

See MOS:COLOR for information about restrained use of color in tables, to avoid creating accessibility problems for visually-impaired as well as normal vision readers.

Do not separate items by leaving blank lines between them, even when using unordered or definition lists. The Wikipedia list templates explicitly identify lists for readers, rather than relying on visual formatting to indirectly imply the presence of a list.


Splitting lists and tables per summary style is advised against. Among other problems, arbitrarily splitting a wikitable effectively disables the powerful and useful sorting feature from working across the entire table.

On the other hand, overloading tables with too much detailed statistical data is against policy. Careful thought should be given to how a reader would use a table, and what level of detail is appropriate.




Tables are a way of presenting links, data, or information in rows and columns. They are a complex form of list, formatted into a systematic grid pattern. Tables might be useful for presenting mathematical data such as multiplication tables, comparative figures, or sporting results. They may also be useful for presenting equivalent words in two or more languages; for awards by type and year; complex discographies; etc.

The sortability of multiple columns in a table is a powerful tool that helps the reader to understand relationships and find patterns in large lists. The sortability of tables makes them very useful for "List of..." articles in Wikipedia, which are intended to give an overview of the subject area, and to allow easy comparisons among many similar items. Avoid cramming too much detailed information into individual table entries; if appropriate, the reader should be able to click a Wikilink to read a full, detailed article corresponding to a concise table entry.

Often a list is best left as a list. Before reformatting a list into table form, consider whether the information will be more clearly conveyed by virtue of having rows and columns. If so, then a table is probably a good choice. If there is no obvious benefit to having rows and columns, then a table is probably not the best choice.

Tables should not be misused to resolve visual layout problems. If the information you are editing is not tabular in nature, it probably does not belong in a table: Do not misuse tables for putting a caption under a photograph, arranging a group of links, or other strictly visual features. These practices make the article harder for other Wikipedians to edit, and is likely to cause problems when viewed on different display sizes and aspect ratios. Also, when compared with tables, wikimarkup is more flexible, easier to use, and less arcane when used correctly for desktop publishing layout, page elements, and page orientation and positioning.











If a list is simple, it is generally better to use one of the standard Wikipedia list formats instead of a table. Lists are easier to maintain than tables, and are often easier to read.

Here is an example of a simple list using list formatting:

* 1980: Ultra Wave
* 1988: What's Bootsy Doin'?
* 1994: Blasters of the Universe
* 1994: Fresh Outta 'P' Uni

Which produces:

  • 1980: Ultra Wave
  • 1988: What's Bootsy Doin'?
  • 1994: Blasters of the Universe
  • 1994: Fresh Outta 'P' Uni

versus table formatting:

|Ultra Wave
|What's Bootsy Doin'?
|Blasters of the Universe
|Fresh Outta 'P' Uni

Which produces:

1980 Ultra Wave
1988 What's Bootsy Doin'?
1994 Blasters of the Universe
1994 Fresh Outta 'P' Uni


Prose is preferred in articles as prose allows the presentation of detail and clarification of context, in a way that a table may not. Prose flows, like one person speaking to another, and is best suited to articles, because their purpose is to explain. Tables which are mainly links, which are most useful for browsing subject areas, should usually have their own entries: see Wikipedia:Stand-alone lists for detail. In an article, significant items should normally be mentioned naturally within the text rather than merely tabulated.


Page layouts (using multiple columns, positioning elements, adding borders, etc.) should be done via CSS, not tables, whenever possible.

  • Images and other embedded media should be positioned using standard image syntax.
  • There are several templates available that will create preformatted multi-column layouts: see Help:Columns.
  • Other elements can be positioned or given special formatting through the use of the HTML <div> element and CSS styling.



  1. ^ 1.0 1.1 1.2 1.3 1.4 Turner, Chris. World Professional Championship. cajt.pwp.blueyonder.co.uk. Chris Turner's Snooker Archive. [18 March 2011]. 
  2. ^ 2.0 2.1 Turner, Chris. International Open Goya, Matchroom Trophy. cajt.pwp.blueyonder.co.uk. Chris Turner's Snooker Archive. [18 March 2011]. 
  3. ^ Turner, Chris. Classic. cajt.pwp.blueyonder.co.uk. Chris Turner's Snooker Archive. [18 March 2011]. 
  4. ^ 4.0 4.1 Turner, Chris. UK Championship. cajt.pwp.blueyonder.co.uk. Chris Turner's Snooker Archive. [18 March 2011]. 
  5. ^ Top Albums/CDs – Volume 58, No. 25. RPM (Library and Archives Canada). January 10, 1994 [August 15, 2010]. 
  6. ^ IFPI Platinum Europe Awards: 2002 Awards. International Federation of the Phonographic Industry (IFPI) – Europe. [August 15, 2010].