Template:Infobox bird/doc

The infobox can be used to display avian measurements. An infobox is placed below the taxobox. Here is a sample:

General settings

 * Set  to make the box collapsible.
 * Set  to make the box collapsible.


 * Determines the initial collapsed state of the infobox. Set  to put the box in collapsed state initially. Set   to put the box in expanded state initially. Set   to have the box's initial collapsed state be determined automatically based on the number of other templates in the article that also have the "collapsible" attribute. (Has no effect if   is not used)
 * Determines the initial collapsed state of the infobox. Set  to put the box in collapsed state initially. Set   to put the box in expanded state initially. Set   to have the box's initial collapsed state be determined automatically based on the number of other templates in the article that also have the "collapsible" attribute. (Has no effect if   is not used)

Bird specific
The infobox supports up to 4 populations or subspecies, each having its own pop and data parameter. The data parameter should be filled in with Infobox bird/population and its respective data.

Each Infobox bird/population should have the unit parameter filled in. Examples:


 * in (displays inches and millimetres)
 * mm (displays millimetres and inches)
 * cm (displays centimetres and inches)

The Infobox bird/population has several optional parameters, including all of the following:


 * length
 * culmen
 * head (bill-tip to back of skull)
 * wing
 * wingspan
 * tail
 * tarsus
 * foot (tarsus + longest toe used mainly for cranes and bustards}
 * weight (requires massunit to be used, which accepts "lb", "kg", "g", or "oz")

All of these parameters are designed to accept either a number or two numbers with a hyphen in the middle.

Examples:
 * 30
 * 100-200
 * 40oz

If a measurement is gender-specific, you can specify the gender by adding "m" or "f" to the parameter name, as in lengthm.

Known issues
Supports only four sections. References cannot be added to specific measurements. The infobox should NEVER be nested within a transcluded template. The expansion depth is large, due to the nesting of convert and some string manipulators. If such a nested transclusion must be made, be sure not to include hyphenated ranges, as they will assuredly break.

You can make this template better!
That's right-- if you feel like improving the infobox, one place to start is by reducing the nested function calls in convert, or by creating a lightweight version for use with the infobox.