Write ICU plural and select messages

English has two plural forms, so English-speaking developers write count === 1 ? "item" : "items" and ship it. CLDR defines up to six categories (zero, one, two, few, many, other), and which numbers fall into each depends on the locale: 21 is "one" in Russian, 1.5 is "one" in French but "other" in English, and Japanese has only "other". ICU MessageFormat handles all of this, but only when every branch is a full sentence, other is always present, the number is written as #, and the categories match each locale.

Convert these messages to ICU MessageFormat for the locales [LOCALES]:

[MESSAGES]

1. For each message, identify the variables and their kinds: a count (cardinal plural), a rank (ordinal, selectordinal), gender or another category (select), or plain interpolation.
2. Write the source-language message first:

• Use # for the formatted count inside plural branches.
• Use =0 (or any exact =N) only for wording that is genuinely special ("No messages"), never as a stand-in for a plural category.
• Use offset:1 for patterns like "You and # others".
• Put select outside and plural inside when both apply, and make every branch a complete sentence. Never assemble fragments around a plural.
• Every plural, select and selectordinal has an other branch.
• Escape a literal apostrophe as '' and literal braces with apostrophe quoting.

1. For each target locale, list its CLDR cardinal categories (and ordinal categories if used), then write the message with exactly those branches plus any exact matches. Translations: draft. With draft, translate every branch with the grammar the category needs (case and agreement change between few and many, not only the noun ending) and mark each locale as needing review by a native speaker; if you cannot translate a locale reliably, fall back to TODO text for it and say so. With structure-only, write TODO text in every branch, with a translator note naming the number range each branch covers.
2. Choose test values that hit every category in each locale, including the tricky ones: 0, 1, 2, a few-range value, 5, 11, 21, 22, 101, 1.5, and a large number such as 1000000 where the locale has a many category for it.
3. If a runtime is available, verify categories with Intl.PluralRules (or the ICU library) and say you did. Otherwise state that the categories come from CLDR rules.

• Never translate ICU keywords, argument names or category names.
• Do not reduce a locale's categories to make messages shorter; missing categories fall back to other and read wrongly.
• If a message cannot work as ICU without a copy change (for example, a count embedded in a fragment shared across messages), say so and propose the reworded source.
• Separate what you verified from what you inferred. Mark inferences as such.
• When you do not know, say "I don't know" once and state what would settle it.

Messages

For each key: the source message, then one code block per locale, headed by the locale and its category list.

Test values

| Key | Locale | Value | Category | Expected output |

Notes

Copy changes needed, translations to review, and any category you could not confirm.