You're reading from Effective Angular Develop applications of any size by effectively using Angular with Nx, RxJS, NgRx, and Cypress

Product type Paperback

Published in Aug 2024

Publisher Packt

ISBN-13 9781805125532

Length 400 pages

Edition 1st Edition

Languages

Typescript

Tools

Angular

Concepts

Application Development

Author (1):

Roberto Heckers

View More author details

Table of Contents (18) Chapters

Preface

1. Part 1:Angular Basics and Setting Up Scalable Nx Workspaces FREE CHAPTER

2. Chapter 1: Scalable Front-End Architecture for Angular Applications

3. Chapter 2: Powerful Angular Features

4. Chapter 3: Enhancing Your Applications with Directives, Pipes, and Animations

5. Chapter 4: Building Forms Like a Pro

6. Part 2:Handling Application State and Writing Cleaner, More Scalable Code

7. Chapter 5: Creating Dynamic Angular Components

8. Chapter 6: Applying Code Conventions and Design Patterns in Angular

9. Chapter 7: Mastering Reactive Programming in Angular

10. Chapter 8: Handling Application State with Grace

11. Part 3:Getting Ready for Production with Automated Tests, Performance, Security, and Accessibility

12. Chapter 9: Enhancing the Performance and Security of Angular Applications

13. Chapter 10: Internationalization, Localization, and Accessibility of Angular Applications

14. Chapter 11: Testing Angular Applications

15. Chapter 12: Deploying Angular Applications

16. Index

Why subscribe?

17. Other Books You May Enjoy

Adding translatable content in Angular applications

In this section, we will dive into internationalization, commonly referred to as i18n (i18n is the abbreviation for internationalization, where “i” and “n” are the first and last letters of the word, and 18 stands for the number of letters in between the “i” and the “n”). Internationalization is developing usable applications for people who speak different languages. Simply put, when you implement i18n, you make your application content translatable. About 75% of the world doesn’t speak English at all, so if you only display your application content in English (or exclusively use another language), you are missing out on a lot of potential users.

The Angular framework has built-in functionalities to support translatable content, but we will not be using the built-in i18n solution to support translatable content. The first reason is that the built-in solution used XML...