Skip to content

ICU Message Syntax

Crowdin Enterprise supports ICU Message syntax, which is used to help express the subtleties of language-specific spelling, grammar, and formatting in translations.

Strings formatted in the ICU Message syntax can have different types of replacements called arguments. Each argument is enclosed in single curly braces (e.g., {variable}) and refers to a value in the input data. Please note that using double curly braces (e.g., {{variable}}) is not supported and will cause syntax errors. Arguments of the following types are supported in Crowdin Enterprise: number, date, time, select, and plural.

ICU syntax arguments are always highlighted in the Editor, so you know which part of the string shouldn’t be translated. Change the position of arguments in translation to follow the natural word order in the target language. There’s also a preview mode, that allows you to see how the translation will be displayed in the UI to make sure that all the translatable elements are translated.

ICU Message syntax in the Editor

Plural type is used to handle plural category variations, as each language has its own set of plural categories (for example, English has “one” and “other”, while Ukrainian has “one”, “few”, “many”, and “other”).

You {itemCount, plural,
=0 {have no projects}
one {have # project}
other {have # projects}
}.

The following short tags are used to determine the plural categories:

  • zero
  • one (singular)
  • two (dual)
  • few (paucal)
  • many (also used for fractions if they have a separate class)
  • other (required—general plural form—also used if the language only has a single form)

In the Editor, you don’t have to manually add or delete plural categories to the translations you are making. Just click Copy Source, and the source string will be copied to the translation field with the number of plural categories right for the current target language.

Read more about Language Plural Rules.

In some cases, you may have a single string that contains multiple nouns that each need to be pluralized independently, for example, “You have X book(s) and Y pen(s).”

ICU handles this by allowing you to nest plural arguments inside each other.

{bookCount, plural,
one {You have # book and {penCount, plural,
one {# pen}
other {# pens}
}}
other {You have # books and {penCount, plural,
one {# pen}
other {# pens}
}}
}

The purpose of the select ordinal type is to choose output based on the ordinal pluralization rules (1st, 2nd, 3rd, etc.) of the current target language. It is very similar to the plural type, except the value is mapped to an ordinal plural category.

Congrats! It's your {year, selectordinal,
one {#st}
two {#nd}
few {#rd}
other {#th}
} subscription anniversary!

Select type is used to choose an output based on a string variable. It is most commonly used to represent the right gender-based inflections in the message.

{gender, select,
male {He uses}
female {She uses}
other {They use}
} Crowdin.

This type is useful for any situation where the translation changes based on a specific keyword. Regardless of the use case, the ICU standard requires that you always include an other clause. This clause provides a necessary fallback in case the variable doesn’t match any of the specified options.

The purpose of the number type is to display different number values such as percentage, currency, and decimal numbers independently of the locale conventions for those. This enables adjustment of the message output to the number formats used in different locales. ICU Number Skeletons are also supported.

The app price is {price, number, ::currency/USD} with {discount, number, percent} discount.

Date and time types show date and time values according to the formats preferred in the specified locales. These types can also have a style – extra information on how the value will be formatted. The following four styles can be used: short, medium, long, and full.

Your meeting is scheduled for {dateValue, date, long} at {timeValue, time, short} AM.

Syntax error detection significantly reduces confusion when translating strings with ICU Message syntax, as the platform automatically detects potential translation errors. If a syntax error is found, you’ll see a notice with a suggestion of what needs to be fixed.

You can also use external tools to verify your ICU syntax, for example, the Online ICU Message Editor.

Syntax error detected
Was this page helpful?