Intermediate Localization Eng. #icu#plural-rules#i18n

ICU MessageFormat — Advanced Patterns Vocabulary

Q: How many exercises are in this module?

This module has 5 multiple-choice exercises, each with instant feedback and a full explanation of the correct answer.

Q: Is this exercise free to use?

Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.

Q: Do I need to create an account to do these exercises?

No account is required. Just click an option to answer — your score for this session is tracked automatically in the progress bar above.

Q: What happens if I choose the wrong answer?

You'll immediately see which answer was correct, plus a full explanation covering the vocabulary and reasoning behind it — mistakes are where most of the learning happens.

Q: Can I retry the exercises if I want a higher score?

Yes — use the "Try again" button on the results screen to reset and go through all the questions again.

Q: Is my progress saved if I close the page?

No. Progress is tracked only for your current visit; reloading or leaving the page resets the counter. This keeps the exercise simple and account-free.

Q: Where can I find more Localization Engineering Language exercises?

Browse the full Localization Engineering Language hub for related drills, or check the "Next up" link below to continue with a connected topic.

Q: How is this different from reading an article on the same topic?

Articles explain vocabulary and concepts in prose; this exercise tests and reinforces that vocabulary through active recall with immediate feedback — the two work best together.

Q: Who writes these exercises?

Every exercise is written by the CoderSlingo team, drawing on real workplace English used in IT roles, then reviewed for accuracy and clarity.

5 exercises — 5 exercises practising ICU MessageFormat plural rules, select expressions, nested patterns, and date/number format skeletons.

0 / 5 completed

1 / 5

A developer asks: "Why do we need ICU MessageFormat for plurals? Can't we just do count === 1 ? 'item' : 'items'?" Which explanation is correct?

2 / 5

A localization engineer reviews a message: {gender, select, male {He replied to your comment} female {She replied to your comment} other {They replied to your comment}}. What ICU pattern is this and what is the purpose of the other

    
  
  
  
 
  
 The select pattern is ICU's case-switching mechanism for non-numeric values — gender, tense, grammatical case, or any enum-like value that affects phrasing.

The other case in select is not optional — ICU requires it as the default for any value not explicitly matched. This is critical for robustness: if a user's gender data is missing or set to a value not in the pattern, other provides a grammatically neutral fallback. Best practices: always use other as a grammatically inclusive fallback (e.g., "they" in English), not as an error case. Languages where select is essential: Spanish ("él respondió" vs. "ella respondió"), German (noun gender affects articles: "der/die/das"), Russian (grammatical cases change verb and adjective endings based on subject gender).

Key vocabulary:
• ICU select pattern — {variable, select, case1 {...} other {...}}; switches on a string value
• other (select) — required default case; triggered by any value not explicitly listed in the pattern
• gender-aware messaging — using select to provide grammatically correct phrases based on user gender/pronoun preference

 3 / 5
 A developer encounters this ICU pattern and asks what it does: {count, plural, one {{name} liked your photo} other {{name} and {count} others liked your photo}}. Is this valid ICU, and what does the double {{ indicate?
    
  
  
  
 
  
 ICU allows free variable interpolation inside plural and select cases — the nested {name} is a standard placeholder, not special syntax.

The # symbol inside plural cases is a shorthand for the plural count value (equivalent to {count} as a number). But you can also use the full {count} if you need it formatted differently (e.g., with a specific number format). Other variables like {name} work the same as anywhere else. Complex real-world example: {numPhotos, plural, one {{name} shared 1 new photo with {numFriends, plural, one {1 friend} other {# friends}}} other {{name} shared # new photos with {numFriends, plural, one {1 friend} other {# friends}}}} — nested plural inside plural with shared variable reference.

Key vocabulary:
• ICU placeholder — {variableName} inside a message pattern; replaced at runtime with the provided argument value
• # (in plural) — shorthand for the formatted plural count value within a plural case
• nested ICU patterns — plural or select patterns nested inside other plural/select cases; valid but increases translator complexity

 4 / 5
 A backend developer is formatting a date for display in multiple locales and asks about ICU date skeleton patterns. How do these differ from fixed date format strings like dd/MM/yyyy?
    
  
  
  
 
  
 Date skeletons specify WHAT fields to show, not HOW to order them — the locale determines the order and separators, producing culturally correct output automatically.

The problem with hardcoded formats: dd/MM/yyyy works for UK users but confuses US users who expect MM/dd/yyyy. Japanese users expect yyyy/MM/dd. German users prefer dd.MM.yyyy. Instead of maintaining separate format strings per locale, use a skeleton: new Intl.DateTimeFormat(locale, {year: 'numeric', month: '2-digit', day: '2-digit'}).format(date) — same JavaScript, correct locale-specific output. ICU skeletons in message strings: {date, date, ::yMMMd} formats a date with year, 3-letter month, and day in the locale-appropriate order and style.

Key vocabulary:
• date skeleton — ICU notation specifying date/time fields to include; locale determines field ordering
• date format string — explicit pattern (dd/MM/yyyy) that produces the same output regardless of locale (avoid for localization)
• Intl.DateTimeFormat — JavaScript built-in using CLDR locale data to format dates correctly per locale

 5 / 5
 A localization engineer identifies a bug: the French translation of an ICU plural message is missing the few and many plural categories. Is this a problem for French?
    
  
  
  
 
  
 Plural categories are language-specific — providing categories a language doesn't use wastes effort; omitting categories a language does use causes incorrect output.

French plural rules (CLDR): one → numbers 0 and 1 (unusually, 0 uses singular in French), other → 2 and above. French does not use two, few, many, or zero categories. So a French translator only needs to provide: {count, plural, one {# élément} other {# éléments}}. If they were asked to provide few and many as well, those values would never be used. Contrast with Arabic (uses all 6), Russian (uses one/few/many/other), or Polish (uses one/few/many/other with complex rules). The ICU runtime uses CLDR to determine which case to apply for a given number in the active locale — unused categories are simply never triggered.

Key vocabulary:
• plural category coverage — translators should only provide the CLDR categories applicable to their language
• CLDR plural rules — language-specific rules mapping number values to plural category names
• one (French plural) — French uses one category for both 0 and 1; unlike English where 0 uses other

  
 
   Back to Localization Engineering Language 
 Next up: LLM-Assisted and Machine Translation →

  Frequently Asked Questions
   What will I practise in "ICU MessageFormat — Advanced Patterns Vocabulary — Localization Engineering | CoderLingo"?
 5 exercises practising ICU MessageFormat plural rules, select expressions, nested patterns, and date/number format skeletons.
 
 How many exercises are in this module?
 This module has 5 multiple-choice exercises, each with instant feedback and a full explanation of the correct answer.
 
 Is this exercise free to use?
 Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
 
    Do I need to create an account to do these exercises?
 No account is required. Just click an option to answer — your score for this session is tracked automatically in the progress bar above.
 
 What happens if I choose the wrong answer?
 You'll immediately see which answer was correct, plus a full explanation covering the vocabulary and reasoning behind it — mistakes are where most of the learning happens.
 
 Can I retry the exercises if I want a higher score?
 Yes — use the "Try again" button on the results screen to reset and go through all the questions again.
 
 Is my progress saved if I close the page?
 No. Progress is tracked only for your current visit; reloading or leaving the page resets the counter. This keeps the exercise simple and account-free.
 
 Where can I find more Localization Engineering Language exercises?
 Browse the full Localization Engineering Language hub for related drills, or check the "Next up" link below to continue with a connected topic.
 
 How is this different from reading an article on the same topic?
 Articles explain vocabulary and concepts in prose; this exercise tests and reinforces that vocabulary through active recall with immediate feedback — the two work best together.
 
 Who writes these exercises?
 Every exercise is written by the CoderSlingo team, drawing on real workplace English used in IT roles, then reviewed for accuracy and clarity.