Help:Lists/cs

Tato stránka popisuje, jak se v MediaWiki vytvářejí seznamy.



Základní informace
offers three types of lists: unordered lists, ordered lists and definition lists.

Basically

 * Unordered lists
 * Each item is on a new line starting with an asterisk  e.g..


 * Ordered lists
 * Each item is on a new line starting with a hash  e.g..


 * Definition lists
 * Each item has two parts : the term and the description
 * The term is on a new line starting with a semicolon  e.g..
 * The description follows on the same line after a colon  e.g. ,
 * or the description starts its own line with a colon  e.g.   (there can be several descriptions per term, each one starting with a colon on a new line).

A little bit further
In the following table you will find some examples for both methods:

Multiple line in lists
For simplicity, list items in wiki markup cannot be longer than a paragraph. A following blank line will end the list and reset the counter on ordered lists. Separating unordered list items usually has no noticeable effects.

Paragraphs can be forced in lists by using HTML tags. If you want to put more than one line of text, add two line break symbols,, and you will get the desired effect. Wrapping text in will render that text in a new paragraph, which will start on its own line when rendered.

Continuing a list item after a sub-item
In HTML, a list item may contain several sublists, not necessarily adjacent; thus there may be parts of the list item not only before the first sublist, but also between sublists, and after the last one. However, in wiki-syntax, sublists follow the same rules as sections of a page: the only possible part of the list item not in sublists is before the first sublist.

In the case of an unnumbered first-level list in wikitext code this limitation can be overcome by splitting the list into multiple lists; indented text between the partial lists may visually serve as part of a list item after a sublist; however, this may give, depending on CSS, a blank line before and after each list, in which case, for uniformity, every first-level list item could be made a separate list.

Numbered lists illustrate that what should look like one list may, for the software, consist of multiple lists; unnumbered lists give a corresponding result, except that the problem of restarting with 1 is not applicable.

One level deeper, with a sublist item continuing after a sub-sublist, one gets even more blank lines; however, the continuation of the first-level list is not affected:

See also.

It is possible to embed unnumbered bullets inside enclosing numbered items:

Per list
The list type (which type of marker appears before the list item) can be changed in CSS by setting the list-style-type property:

Site-wide
The standard #, ##, ### wikitext can be used alongside CSS in MediaWiki:Common.css to produce the usual system of numbered lists (1, 2, 3; then a, b, c; then i, ii, iii):

The first  above is the default, so not necessary unless some other list-style-type is required.

Extra indentation of lists
In a numbered list in a large font, some browsers do not show more than two digits, unless extra indentation is applied (if there are multiple colons: for each colon). This can be done with CSS:

or alternatively, like below.

To demonstrate that all three methods show all digits of 3-digit numbers, see List demo.

Specifying a starting value
Specifying a starting value is possible with HTML syntax.

Or:

Comparison with a table
Apart from providing automatic numbering, the numbered list also aligns the contents of the items, comparable with using table syntax:

gives:

This non-automatic numbering has the advantage that if a text refers to the numbers, insertion or deletion of an item does not disturb the correspondence.

Multi-column lists
See also Template:Col-begin, Template:Col-break, Template:Col-end.

Multi-column bulleted list
gives:


 * apple
 * carpet
 * geography
 * mountain
 * nowhere
 * postage
 * ragged
 * toast

gives:


 * apple
 * carpet
 * geography
 * mountain
 * nowhere
 * postage
 * ragged
 * toast

Multi-column numbered list
gives:


 * 1) apple
 * 2) carpet
 * 3) geography
 * 4) mountain
 * 5) nowhere
 * 6) postage
 * 7) ragged
 * 8) toast

Below a starting value is specified, with HTML-syntax (for the first column either wiki-syntax or HTML-syntax can be used).

In combination with the extra indentation explained in the previous section:

gives

Using the computation of the starting values can be automated, and only the first starting value and the number of items in each column except the last has to be specified. Adding an item to, or removing an item from a column requires adjusting only one number, the number of items in that column, instead of changing the starting numbers for all subsequent columns.

gives:

gives:

gives:

gives:

Streamlined style or horizontal style
It is also possible to present short lists using very basic formatting, such as:

Title of list: example 1, example 2, example 3

Title of list: example 1, example 2, example 3

This style requires less space on the page, and is preferred if there are only a few entries in the list, it can be read easily, and a direct edit point is not required. The list items should start with a lowercase letter unless they are proper nouns.

Tables
A one-column table is very similar to a list, but it allows sorting. If the wikitext itself is already sorted with the same sortkey, this advantage does not apply. A multiple-column table allows sorting on any column.

See also When to use tables.

Changing unordered lists to ordered ones
With the CSS

unordered lists are changed to ordered ones. This applies (as far as the CSS selector does not restrict this) to all ul-lists in the HTML source code:


 * those produced with *
 * those with in the wikitext
 * those produced by the system

Since each special page, like other pages, has a class based on the pagename, one can separately specify for each type whether the lists should be ordered. See also User contributions and What links here.

However, it does not seem possible to make all page history lists ordered (unless one makes all lists ordered), because the class name is based on the page for which the history is viewed.