Unit Names and Patterns

These are intended for stand-alone use such as the label of a field where values may be entered, for example Minutes and Seconds in the example below.

Enter desired time to liftoff:
 Minutes:    Seconds:  

The expectation is that the display names would be in nominative form for languages in which it makes a difference. There may be cases in which a display name could be used in contexts for which nominative would be inappropriate, but the hope is that CLDR clients would arrange the use of display names in user interfaces so that nominative form is not inappropriate.

The unit data is provided in three widths:
  • long: typically a fully spelled-out name
  • short: a distinctive abbreviated form, not easily confused with another unit
  • narrow: as short as possible for situations with limited display space. Typically this form eliminates spaces and punctuation to the extent possible, and uses abbreviations that might only be clear in context.
Note that if in your locale certain abbreviations are always understood to mean particular units, then different abbreviations should generally be used even in the narrow form for other units. For example, if “m” is always understood to mean “meters”, then even in the narrow form a different abbreviation should be used for “minutes”—perhaps “min”, “mn”, or even “m.”.

Simple Units

Simple units are cases like "{0} mile" or "{0} miles". These have from 1 to 6 plural forms, depending on the language. Units also have a display name, such as "miles", used as labels in interfaces.

Compound Units

Some units are compound units, like "miles per hour". When formatting, software will first look for a specialized pattern (with the right plural form), then if that is not available, look for a compound unit and compose a fallback format. Hover over the English column and the Winning column to see examples. The following patterns are available:

  Pattern Examples Formatted Examples Description
per {0} per {1} cm/s, centimeters per second Used to compose units consisting of a division of two source units when there is no specialized pattern available. See perUnitPatterns.
times {0}-{1} kW⋅h,
kilowatt-hour
Used to compose units consisting of a multiplication of two source units when there is no specialized pattern available. See kilowatt hour.
power
(square, cubic)
square {0} square meters • Used to compose area or volume measures when there is no specialized pattern available. The width should correspond to the base unit's width, as in {0} square meter or {0} m².
• The short form will typically be superscripts {0}² or {0}³; the long form may be the same or may be spelled out (as in English). Inflected languages may need to use the superscripts instead of spelled-out forms where the units may have different genders that would force adjective agreements.
• Note that the base unit will be lowercased when there is no spacing around the {0}. Thus {0} Meter will be lowercased when composed with Quadrat{0}.
prefix
(milli-,
kilo-,…)
milli{0} millimeter • Used to compose metric units when there is no specialized pattern available.
• The width should correspond to the base unit's width, as in {0} decimeter or {0} dm.
• Note that the base unit will be lowercased when there is no spacing around the {0}. Thus {0} Meter will be lowercased when composed with Milli{0}.
• There are two different sets of prefixes:
   • The standard prefixes are base 10, such as mega{0} = ×10⁶ = ×1,000,000.
   • The binary prefixes are base 1024, such as mebi{0} = ×1024² = ×1,048,576. There are only a few of these, and they are only used with digital units such as byte or bit. See Mebibyte for more information.

Using these patterns, names for complex units can be formed, such as gigawatt hour per square second. In common cases, these complex units will have an explicit translation that you supply such as kilowatt-hour. But for less common cases, the components will be used to form units, and you need to make sure that they are consistent.

Common Problems with Compound Units

Make sure that the prefix patterns are consistent with the explicit translations. Here are some common problems to watch for.

Descriptions Examples
Prefix is the wrong format, such as having a hyphen when the explicit compound doesn't «γιγα-{0}» produces «{0} γιγα-χερτζ», but the explicit translation is «{0} γιγαχέρτζ»
The spacing for the simple unit pattern differs from the spacing for the explicit compound (including non-breaking vs breaking space) «hecto{0}» produces «{0} hectopascals», but the explicit translation is «{0} hectopascals»
The translation of the core unit is different than the translation of the explicit compound «M{0}» produces «{0} Mbyte», but the explicit translation is «{0} MB»
«n{0}» produces «{0} nsec», but the explicit translation is «{0} ns»
«{0}²» produces «{0} μ.²», but the explicit translation is «{0} m²»
The translation is incomplete, for example: the "one" form «{0} carré» was translated, but not the plural form, which inherits {0}² from root«{0}²» produces «{0} mètres²», but the explicit translation is «{0} mètres carrés»

Important: languages are complicated, and sometimes the composition of complex units cannot match what is grammatically correct for your language. Sometimes there are no fixes that you can make to fix the issue completely. So any indications of problems are warnings, not errors. For example, here is an issue that the translator can't fix:

Descriptions Examples
The accent needs to shift when a prefix is added «δεκατο{0}» produces «{0} δεκατολίτρα», but the explicit translation is «{0} δεκατόλιτρα»
The internal algorithm for when to combine spacing needs adjustment. M{0}» produces «{0}M o», but the explicit translation is «{0} Mo»


Your goal is to make the composition work as well as you can, even it if is not perfect.

Specialized Pattern

The specialized patterns are needed where there is a special abbreviation, like "mph" instead of "m/hr".

In addition, there are some very common combinations that are translated as a whole, such as "{0} kilometro par hora". In that case, the number is substituted directly for the {0} placeholder.

Per Unit Pattern

In many languages, the "per Y" part is inflected, and the dividing unit can't be simply substituted for {1}. Because of that, there are "per unit" patterns that are of the form "{0} per hour". For that case, the process is simpler. The first two steps are the same, but then the result is substituted into the "{0} per hour" pattern directly.

Fallback Format: two units

Some units are formed by combining other units. The most common of this is X per Y, such as "miles per hour". There is a "per" pattern that is used for this. For example, "{0} per {1}" might get replaced by "10 meters per second". 

Given an amount, and two units, the process uses the available patterns to put together a result, as described on perUnitPatterns. (e.g. "3 kilograms" + "{0} per second" → "3 kilograms per second")






























Comments