From 733e28245480f7b6c9381a760ac32dd03c2d9cb3 Mon Sep 17 00:00:00 2001
From: "J. Degand" <70610011+jdegand@users.noreply.github.com>
Date: Tue, 3 Sep 2024 04:14:12 -0400
Subject: [PATCH] docs(angular): add translation files content (#6947)

---
 .../content/translation-files@jL5amGV1BAX_V5cyTIH7d.md | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/src/data/roadmaps/angular/content/translation-files@jL5amGV1BAX_V5cyTIH7d.md b/src/data/roadmaps/angular/content/translation-files@jL5amGV1BAX_V5cyTIH7d.md
index 366c2fe12..1748fa844 100644
--- a/src/data/roadmaps/angular/content/translation-files@jL5amGV1BAX_V5cyTIH7d.md
+++ b/src/data/roadmaps/angular/content/translation-files@jL5amGV1BAX_V5cyTIH7d.md
@@ -1 +1,9 @@
-# Translation Files
\ No newline at end of file
+# Translation Files
+
+After you prepare a component for translation, use the `extract-i18n` Angular CLI command to extract the marked text in the component into a source language file. The marked text includes text marked with `i18n`, attributes marked with `i18n`-attribute, and text tagged with `$localize`. The `extract-i18n` command creates a source language file named `messages.xlf` in the root directory of your project.  If you have multiple language files, add the locale to the file name, like `messages.{locale}.xlf`.
+
+Visit the following resources to learn more:
+
+- [@official@Angular Official Docs - Translation Files](https://angular.dev/guide/i18n/translation-files)
+- [@official@Angular Official Docs - Extract i18n](https://angular.dev/cli/extract-i18n)
+- [@article@Angular i18n: internationalization & localization with examples](https://lokalise.com/blog/angular-i18n/)
\ No newline at end of file