Misplaced Pages

:Manual of Style/Tables: Difference between revisions - Misplaced Pages

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
< Misplaced Pages:Manual of Style Browse history interactively← Previous editNext edit →Content deleted Content addedVisualWikitext
Revision as of 13:03, 25 August 2009 editPietrow (talk | contribs)Extended confirmed users, Pending changes reviewers1,539 edits Table Coding -- Reduce clutter: Typography← Previous edit Revision as of 03:42, 27 August 2009 edit undoUnitedStatesian (talk | contribs)Extended confirmed users, Page movers, New page reviewers, Pending changes reviewers, Template editors245,379 edits being bold: no evidence that long lists are harder to edit when in table form (esp. when wikitable is used)Next edit →
Line 15: Line 15:
** Artist, album, year, and label ** Artist, album, year, and label


Often a list is best left as a list. Some articles include very long lists which might be difficult to edit if they were in table form. Before you format a list in 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. Often a list is best left as a list. Before you format a list in 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 used simply for layout, either. If the information you are editing is not tabular in nature, it probably does not belong in a table. Try not to use tables for putting a caption under a photograph, arranging a group of links, or other strictly visual features. It makes the article harder to edit for other Wikipedians, and is not really what tables were designed to do. Tables should not be used simply for layout, either. If the information you are editing is not tabular in nature, it probably does not belong in a table. Try not to use tables for putting a caption under a photograph, arranging a group of links, or other strictly visual features. It makes the article harder to edit for other Wikipedians, and is not really what tables were designed to do.


== When tables are inappropriate == == When tables may not be appropriate ==


=== Very long lists, or very simple lists === === Simple lists ===


If a list is quite long, or is relatively simple, use one of the standard ]. Long lists can be hard to maintain if they are inside a table, and simple lists do not need the row-and-column format that a table provides. Here are some examples of things that might be better done with lists instead of tables. If a list is simple, use one of the standard ]. Simple lists do not need the row-and-column format that a table provides. Here are some examples of things that might be better done with lists instead of tables.


==== Table formatting (Don't do this) ==== ==== Simple List Table formatting (Don't do this) ====
<blockquote style="background: white; border: 1px solid black; padding: 1em;"> <blockquote style="background: white; border: 1px solid black; padding: 1em;">
<table border="1"> <table border="1">
Line 69: Line 69:


== Table Coding — Reduce clutter == == Table Coding — Reduce clutter ==
Where a table is genuinely necessary and desired, use the preformatted '''<nowiki>class="wikitable"</nowiki>''' format, if possible, instead of manually coding a complex HTML table directly in the article. This will make the table, and the article itself, much easier for other people to edit in the future. Where a table is genuinely necessary and desired, use the preformatted '''<nowiki>class="wikitable"</nowiki>''' format, or one of the related formats, instead of manually coding a complex HTML table directly in the article. This will make the table, and the article itself, much easier for other people to edit in the future.


==See also== ==See also==

Revision as of 03:42, 27 August 2009

This guideline is a part of the English Misplaced Pages's Manual of Style.
It is a generally accepted standard that editors should attempt to follow, though occasional exceptions may apply. Any substantive edit to this page should reflect consensus. When in doubt, discuss first on the talk page.
Shortcut

Tables can be useful for a variety of content presentation on Misplaced Pages. This page discusses where it makes sense to use tables. For details on how to create tables using wiki markup, see Help:Table.

When tables are appropriate

Tables are perfect for organizing any information that is best presented in a row-and-column format. This might include:

  • Mathematical tables
    • Multiplication tables
    • Tables of divisors
    • Lookup tables
  • Lists of information
    • Equivalent words in two or more languages
    • Person, birthdate, occupation
    • Artist, album, year, and label

Often a list is best left as a list. Before you format a list in 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 used simply for layout, either. If the information you are editing is not tabular in nature, it probably does not belong in a table. Try not to use tables for putting a caption under a photograph, arranging a group of links, or other strictly visual features. It makes the article harder to edit for other Wikipedians, and is not really what tables were designed to do.

When tables may not be appropriate

Simple lists

If a list is simple, use one of the standard Misplaced Pages list formats. Simple lists do not need the row-and-column format that a table provides. Here are some examples of things that might be better done with lists instead of tables.

Simple List Table formatting (Don't do this)

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

Layout of images

Often images are placed in an article by using a quirk of table rendering. Because a table can be floated to the left or right side of the screen, it has become common practice to use a simple one-celled table to place an image in a particular part of the screen. This was a necessary workaround for old browsers, since it generates a consistent rendering of images in browsers which do not adequately support Cascading Style Sheets. However, by far the majority of browsers in use today should do just fine with style sheets. The recommended practice now is to arrange images using an element called div.

For detailed instructions, see Misplaced Pages:Image use policy and the Misplaced Pages:Extended image syntax. Here's a brief example:

Table formatting (Do not do this)

<table align="right" border="0" cellpadding="0"><tr><td>]</td></tr></table>

Without tables (Do this instead)

]

How it looks

In both of these cases, the result is essentially the same; the image is floated to the right-hand side of the screen, and the surrounding text wraps around it. Here is what it looks like in your browser (with text added):

Covalent bonding is a form of chemical bonding characterized by the sharing of one or more pairs of electrons between atoms, in order to produce a mutual attraction, which holds the resultant molecule together. Atoms tend to share electrons in such a way that their outer electron shells are filled. Such bonds are always stronger than the intermolecular hydrogen bond and similar in strength to or stronger than the ionic bond.

Covalent bonding most frequently occurs between atoms with similar (high) electronegativities, where to completely remove an electron from one atom requires too much energy. Covalent bonds are more common between non-metals, whereas ionic bonding is more common between a metal atom and a non-metal atom.

Covalent bonding tends to be stronger than other types of bonding, such as ionic bonding. Unlike ionic bonds, where ions are held together by a non-directional coulombic attraction, covalent bonds are highly directional. As a result, covalently bonded molecules tend to form in a relatively small number of characteristic shapes, exhibiting specific bonding angles.

Visual layout

Multiple columns, positioning, borders, and so on should be done with CSS—not tables—when possible.

Table Coding — Reduce clutter

Where a table is genuinely necessary and desired, use the preformatted class="wikitable" format, or one of the related formats, instead of manually coding a complex HTML table directly in the article. This will make the table, and the article itself, much easier for other people to edit in the future.

See also

Categories: