Bird
Raised Fist0
Angularframework~15 mins

Marking text for translation in Angular - Mini Project: Build & Apply

Choose your learning style10 modes available
LearnWhyDeepVisualTryChallengeProjectRecallPerf

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Marking Text for Translation in Angular
📖 Scenario: You are building a simple Angular app that will support multiple languages. To prepare your app for translation, you need to mark certain text strings so that translation tools can find them.
🎯 Goal: Create an Angular component that marks text for translation using Angular's i18n attribute.
📋 What You'll Learn
Create an Angular standalone component named TranslateExampleComponent.
Add a heading with the text Welcome to our site marked for translation using the i18n attribute.
Add a paragraph with the text Enjoy your stay! also marked for translation.
Use Angular's recommended syntax for marking text for translation.
💡 Why This Matters
🌍 Real World
Marking text for translation is essential when building apps that support multiple languages, making your app accessible to a global audience.
💼 Career
Many companies require developers to prepare their Angular apps for internationalization to reach users worldwide.
Progress0 / 4 steps
1
Create the Angular component skeleton
Create a standalone Angular component named TranslateExampleComponent with a selector app-translate-example and an empty template.
Angular
Hint

Use @Component decorator with standalone: true and an empty template string.

2
Add a heading marked for translation
Inside the template of TranslateExampleComponent, add an <h1> element with the text Welcome to our site and mark it for translation using the i18n attribute.
Angular
Hint

Use i18n attribute inside the <h1> tag to mark text for translation.

3
Add a paragraph marked for translation
Below the heading, add a <p> element with the text Enjoy your stay! and mark it for translation using the i18n attribute.
Angular
Hint

Use i18n attribute inside the <p> tag to mark text for translation.

4
Complete the component with proper formatting
Ensure the component template includes both the <h1> and <p> elements with their i18n attributes, properly formatted and ready for translation.
Angular
Hint

Check that both elements have the i18n attribute and the correct text inside the template string.

Practice

(1/5)
1. What is the primary purpose of the i18n attribute in Angular templates?
easy
A. To mark text for translation in the app
B. To style text with international fonts
C. To add animations to text elements
D. To bind data to the text content

Solution

  1. Step 1: Understand the role of i18n in Angular

    The i18n attribute is used to mark text that should be translated for different languages.

  2. Step 2: Differentiate from other attributes

    It is not related to styling, animations, or data binding, which are handled by other Angular features.

  3. Final Answer:

    To mark text for translation in the app -> Option A

  4. Quick Check:

    i18n attribute = mark text for translation [OK]
Hint: Remember: i18n means internationalization for translation [OK]
Common Mistakes:
  • Confusing i18n with styling or animations
  • Thinking i18n binds data instead of marking text
  • Assuming i18n is a directive instead of an attribute
2. Which of the following is the correct syntax to mark a paragraph for translation with a description in Angular?
easy
A.

Welcome to our site!

B.

Welcome to our site!

C.

@@desc

D.

Welcome to our site!

Solution

  1. Step 1: Recognize the correct i18n attribute format

    The i18n attribute can include a description or meaning using the syntax i18n="@@desc" to help translators.

  2. Step 2: Check each option's syntax

    Welcome to our site!

    correctly uses i18n="@@desc" inside the paragraph tag. Options B, C, and D misuse the attribute or place description incorrectly.

  3. Final Answer:

    <p i18n="@@desc">Welcome to our site!</p> -> Option D

  4. Quick Check:

    Correct i18n syntax with description =

    Welcome to our site!

    [OK]
Hint: Use i18n="@@description" inside the tag for descriptions [OK]
Common Mistakes:
  • Placing description outside the tag
  • Using i18n-desc instead of i18n
  • Confusing description with translation key
3. Given the template code: 
<h1 i18n="@@titleDesc">Hello, user!</h1>
What will Angular do with this text during the build process?
medium
A. Throw a syntax error because of the @@ prefix
B. Display 'Hello, user!' without any translation
C. Extract 'Hello, user!' for translation with the description 'titleDesc'
D. Ignore the i18n attribute and render the text as is

Solution

  1. Step 1: Understand Angular's i18n extraction

    Angular extracts text marked with i18n for translation and uses the description (after @@) to help translators identify the text.

  2. Step 2: Analyze the given code

    The text 'Hello, user!' will be extracted with the description 'titleDesc' for translation files. No syntax error occurs because @@ is valid for description keys.

  3. Final Answer:

    Extract 'Hello, user!' for translation with the description 'titleDesc' -> Option C

  4. Quick Check:

    i18n extracts text with description = Extract 'Hello, user!' for translation with the description 'titleDesc' [OK]
Hint: @@ means description key for translators in i18n [OK]
Common Mistakes:
  • Thinking @@ causes syntax errors
  • Assuming text is not extracted for translation
  • Believing i18n attribute is ignored at build
4. Identify the error in this Angular template snippet for translation:
<button i18n="Submit button">Submit</button>
medium
A. The i18n attribute should be written as i18n-desc
B. The description should be inside @@, like i18n="@@Submit button"
C. The text 'Submit' should be inside double curly braces {{}}
D. The i18n attribute must be on a <span>, not a <button>

Solution

  1. Step 1: Check the i18n attribute format

    The description or meaning for translation keys must be prefixed with @@ inside the i18n attribute, e.g., i18n="@@Submit button".

  2. Step 2: Validate other options

    i18n can be used on any element, including button. Text does not require curly braces for static content. The attribute i18n-desc is not valid.

  3. Final Answer:

    The description should be inside @@, like i18n="@@Submit button" -> Option B

  4. Quick Check:

    Description needs @@ prefix in i18n attribute [OK]
Hint: Descriptions in i18n need @@ prefix inside quotes [OK]
Common Mistakes:
  • Omitting @@ prefix for descriptions
  • Thinking i18n only works on <span> elements
  • Using i18n-desc instead of i18n
5. You want to mark multiple pieces of text in an Angular template for translation, each with a unique description. Which approach correctly applies this?
hard
A.

Welcome

This is the intro paragraph.

B.

Welcome

This is the intro paragraph.

C.

Welcome

This is the intro paragraph.

D.

Welcome

This is the intro paragraph.

Solution

  1. Step 1: Use unique descriptions with @@ in i18n attribute

    Angular uses the syntax i18n="@@description" to add unique descriptions for each translatable text.

  2. Step 2: Evaluate each option

    Welcome

    This is the intro paragraph.

    correctly uses i18n="@@headerDesc" and i18n="@@introDesc".

    Welcome

    This is the intro paragraph.

    uses invalid i18n-desc.

    Welcome

    This is the intro paragraph.

    misses @@ prefix.

    Welcome

    This is the intro paragraph.

    uses plain text instead of description keys.

  3. Final Answer:

    <h2 i18n="@@headerDesc">Welcome</h2> <p i18n="@@introDesc">This is the intro paragraph.</p> -> Option A

  4. Quick Check:

    Use i18n="@@uniqueDescription" for each text [OK]
Hint: Use @@ prefix in i18n for unique translation descriptions [OK]
Common Mistakes:
  • Using i18n-desc instead of i18n
  • Omitting @@ prefix for descriptions
  • Putting descriptions as plain text in i18n attribute