Why i18n matters in Angular - See It in Action

Why i18n matters

📖 Scenario: You are building a simple Angular app that greets users in different languages. This helps people from different countries feel welcome and understood.

🎯 Goal: Create a small Angular component that shows a greeting message. Use Angular's i18n support to prepare the app for multiple languages.

📋 What You'll Learn

Create a basic Angular component with a greeting message

Add an i18n attribute to the greeting text for translation

Set up a language variable to switch greetings

Use Angular's i18n syntax to mark the text for translation

💡 Why This Matters

🌍 Real World

Many apps need to support users from different countries. Using i18n helps show text in the user's language, making the app friendly and accessible.

💼 Career

Understanding i18n is important for frontend developers working on global applications. It shows you can prepare apps for international users.

1

Create the greeting message

Create an Angular standalone component called GreetingComponent. Inside its template, add a <h1> tag with the text Hello, welcome!.

Angular

import { Component } from '@angular/core';

@Component({
  selector: 'app-greeting',
  standalone: true,
  template: `
    Hello, welcome!
  `
})
export class GreetingComponent {}

// Your code here

Hint

Define a standalone component with a simple template containing the greeting text.

2

Add i18n attribute for translation

Add the Angular i18n attribute i18n to the <h1> tag in the template to mark the greeting text for translation.

Angular

import { Component } from '@angular/core';

@Component({
  selector: 'app-greeting',
  standalone: true,
  template: `
    Hello, welcome!
  `
})
export class GreetingComponent {}

// Add the i18n attribute to the h1 tag

Hint

Use i18n inside the opening tag to mark text for translation.

3

Add a language variable

Inside the GreetingComponent class, add a public string variable called language and set it to 'en'.

Angular

import { Component } from '@angular/core';

@Component({
  selector: 'app-greeting',
  standalone: true,
  template: `
    Hello, welcome!
  `
})
export class GreetingComponent {
  // Add a language variable here
}

Hint

Declare a public variable language and assign it the value 'en'.

4

Complete with i18n setup

Ensure the component template uses the i18n attribute on the greeting text and the language variable is declared in the class. This completes the basic i18n setup for the greeting message.

Angular

import { Component } from '@angular/core';

@Component({
  selector: 'app-greeting',
  standalone: true,
  template: `
    Hello, welcome!
  `
})
export class GreetingComponent {
  language: string = 'en';
  // Finalize the i18n setup here
}

Hint

Check that the template has i18n and the class has the language variable.

Practice

1. Why is i18n important in Angular applications?

easy

A. It improves the app's loading speed significantly.

B. It allows the app to support multiple languages for users worldwide.

C. It automatically fixes bugs in the code.

D. It changes the app's color scheme based on user preference.

Solution

1. Step 1: Understand the purpose of i18n

   i18n stands for internationalization, which means preparing the app to support different languages.

2. Step 2: Identify the benefit in Angular apps

   Using i18n attributes in Angular helps translate text so users worldwide can understand the app.

3. Final Answer:

   It allows the app to support multiple languages for users worldwide. -> Option B

4. Quick Check:

   i18n = multi-language support [OK]

Hint: i18n means internationalization for language support [OK]

Common Mistakes:

• Thinking i18n improves speed
• Confusing i18n with bug fixing
• Believing i18n changes colors

2. Which of the following is the correct way to mark a text for translation in Angular templates?

easy

A. <h1 i18>Welcome</h1>

B. <h1 translate>Welcome</h1>

C. <h1 lang>Welcome</h1>

D. <h1 i18n>Welcome</h1>

Solution

1. Step 1: Recall Angular i18n syntax

   Angular uses the i18n attribute to mark text for translation in templates.

2. Step 2: Compare options

   Only <h1 i18n>Welcome</h1> uses the correct i18n attribute syntax.

3. Final Answer:

   <h1 i18n>Welcome</h1> -> Option D

4. Quick Check:

   Correct i18n attribute = <h1 i18n>Welcome</h1> [OK]

Hint: Look for exact 'i18n' attribute in template tags [OK]

Common Mistakes:

• Using 'translate' instead of 'i18n'
• Using 'lang' attribute incorrectly
• Misspelling 'i18n' as 'i18'

3. Given this Angular template snippet:

<button i18n>Submit</button>

What will happen when you build the app with i18n enabled and provide translations?

medium

A. The button text will remain 'Submit' regardless of language.

B. The app will throw a syntax error during build.

C. The button text will change to the translated word based on user locale.

D. The button will disappear from the UI.

Solution

1. Step 1: Understand i18n attribute effect

   The i18n attribute marks text for translation during build.

2. Step 2: Effect of providing translations

   When translations exist, Angular replaces the original text with the translated version based on user locale.

3. Final Answer:

   The button text will change to the translated word based on user locale. -> Option C

4. Quick Check:

   i18n + translations = translated text [OK]

Hint: i18n text changes with user language if translations exist [OK]

Common Mistakes:

• Assuming text never changes
• Expecting build errors without syntax issues
• Thinking UI elements disappear

4. You added i18n attributes to your Angular app but translations are not showing. What is a likely cause?

medium

A. You forgot to generate and include translation files during build.

B. You used i18n on HTML tags instead of components.

C. You did not import the Angular FormsModule.

D. You used double quotes instead of single quotes in templates.

Solution

1. Step 1: Check translation file usage

   Adding i18n marks text but translations require generated files included in build.

2. Step 2: Identify common mistake

   Forgetting to generate or include translation files means no translated text appears.

3. Final Answer:

   You forgot to generate and include translation files during build. -> Option A

4. Quick Check:

   Missing translation files = no translations shown [OK]

Hint: Always generate and include translation files after adding i18n [OK]

Common Mistakes:

• Thinking i18n works without translation files
• Confusing i18n usage with FormsModule
• Worrying about quote styles in templates

5. You want your Angular app to support English and Spanish using i18n. Which steps must you follow to achieve this?

hard

A. Mark text with i18n, extract messages, create Spanish translation file, build app with Spanish locale.

B. Use i18n only on components, no need for translation files, Angular auto-translates.

C. Add i18n attributes, write translations inline in templates, no build changes needed.

D. Install a third-party library, ignore Angular i18n, manually change text in code.

Solution

1. Step 1: Mark text for translation

   Use i18n attributes in templates to identify text needing translation.

2. Step 2: Extract and create translation files

   Extract messages to generate a base file, then create a Spanish translation file with translated text.

3. Step 3: Build app with Spanish locale

   Build the Angular app specifying the Spanish locale to use the translations at runtime.

4. Final Answer:

   Mark text with i18n, extract messages, create Spanish translation file, build app with Spanish locale. -> Option A

5. Quick Check:

   Proper i18n workflow = Mark text with i18n, extract messages, create Spanish translation file, build app with Spanish locale. [OK]

Hint: Follow full i18n workflow: mark, extract, translate, build [OK]

Common Mistakes:

• Expecting auto-translation without files
• Writing translations inline in templates
• Ignoring Angular's i18n system