diff --git a/aio/content/guide/i18n.md b/aio/content/guide/i18n.md
index 4bcb42a408..cba2241cee 100644
--- a/aio/content/guide/i18n.md
+++ b/aio/content/guide/i18n.md
@@ -54,10 +54,10 @@ If you use JIT, you also need to define the `LOCALE_ID` provider in your main mo
-For more information about Unicode locale identifiers, see the
+For more information about Unicode locale identifiers, see the
[CLDR core spec](http://cldr.unicode.org/core-spec#Unicode_Language_and_Locale_Identifiers).
-For a complete list of locales supported by Angular, see
+For a complete list of locales supported by Angular, see
[the Angular repository](https://github.com/angular/angular/tree/master/packages/common/locales).
The locale identifiers used by CLDR and Angular are based on [BCP47](http://www.rfc-editor.org/rfc/bcp/bcp47.txt).
@@ -101,10 +101,10 @@ specify a custom locale id. For example, Angular's locale data defines the local
"fr". You can use the second parameter to associate the imported French locale data with the custom
locale id "fr-FR" instead of "fr".
-The files in `@angular/common/locales` contain most of the locale data that you
+The files in `@angular/common/locales` contain most of the locale data that you
need, but some advanced formatting options might only be available in the extra dataset that you can
import from `@angular/common/locales/extra`. An error message informs you when this is the case.
-
+
@@ -113,15 +113,15 @@ import from `@angular/common/locales/extra`. An error message informs you when t
All locale data used by Angular are extracted from the Unicode Consortium's
Common Locale Data Repository (CLDR).
-
+
## Template translations
- This document refers to a unit of translatable text as "text," a "message", or a
- "text message."
+ This document refers to a unit of translatable text as "text," a "message", or a
+ "text message."
@@ -168,7 +168,7 @@ To mark the greeting for translation, add the `i18n` attribute to the `` tag
{@a help-translator}
### Help the translator with a description and meaning
-To translate a text message accurately, the translator may need additional information or context.
+To translate a text message accurately, the translator may need additional information or context.
You can add a description of the text message as the value of the `i18n` attribute, as shown in the
example below:
@@ -176,7 +176,7 @@ example below:
-The translator may also need to know the meaning or intent of the text message within this particular
+The translator may also need to know the meaning or intent of the text message within this particular
app context.
You add context by beginning the `i18n` attribute value with the _meaning_ and
@@ -192,7 +192,7 @@ The Angular extraction tool preserves both the meaning and the description in th
source file to facilitate contextually-specific translations, but only the combination of meaning
and text message are used to generate the specific id of a translation. If you have two
similar text messages with different meanings, they are extracted separately. If you have two similar
-text messages with different descriptions (not different meanings), then they are extracted only once.
+text messages with different descriptions (not different meanings), then they are extracted only once.
{@a custom-id}
@@ -208,7 +208,7 @@ When you change the translatable text, the extractor tool generates a new id for
You must then update the translation file with the new id.
Alternatively, you can specify a custom id in the `i18n` attribute by using the prefix `@@`.
-The example below defines the custom id `introductionHeader`:
+The example below defines the custom id `introductionHeader`:
@@ -220,7 +220,7 @@ custom id.
The custom id is persistent. The extractor tool does not change it when the translatable text changes.
-Therefore, you do not need to update the translation. This approach makes maintenance easier.
+Therefore, you do not need to update the translation. This approach makes maintenance easier.
#### Use a custom id with a description
@@ -266,7 +266,7 @@ the same text, `Bonjour`:
Bonjour
```
-
+
{@a no-element}
@@ -474,7 +474,7 @@ file. This information is not used by Angular, but external translation tools ma
## Translate text messages
The `ng xi18n` command generates a translation source file named `messages.xlf` in the project `src`
-folder.
+folder.
The next step is to translate this source file into the specific language
translation files. The example in this guide creates a French translation file.
@@ -526,7 +526,7 @@ This sample file is easy to translate without a special editor or knowledge of F
> This XML element represents the translation of the `` greeting tag that you marked with the
- `i18n` attribute earlier in this guide.
+ `i18n` attribute earlier in this guide.
> Note that the translation unit `id=introductionHeader` is derived from the
[custom `id`](#custom-id "Set a custom id") that you set earlier, but
@@ -573,7 +573,7 @@ To translate a `plural`, translate its ICU format match values:
-You can add or remove plural cases, with each language having its own cardinality. (See
+You can add or remove plural cases, with each language having its own cardinality. (See
[CLDR plural rules](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html).)
{@a translate-select}
@@ -609,7 +609,7 @@ Here they are together, after translation:
{@a translate-nested}
### Translate a nested expression
-A nested expression is similar to the previous examples. As in the previous example, there are
+A nested expression is similar to the previous examples. As in the previous example, there are
two translation units. The first one contains the text outside of the nested expression:
@@ -683,28 +683,40 @@ You also need to instruct the AOT compiler to use your translation configuration
* `i18nLocale`: the locale id.
```
-"configurations": {
+"build": {
...
- "fr": {
- "aot": true,
- "outputPath": "dist/my-project-fr/",
- "i18nFile": "src/locale/messages.fr.xlf",
- "i18nFormat": "xlf",
- "i18nLocale": "fr",
+ "configurations": {
...
+ "fr": {
+ "aot": true,
+ "outputPath": "dist/my-project-fr/",
+ "i18nFile": "src/locale/messages.fr.xlf",
+ "i18nFormat": "xlf",
+ "i18nLocale": "fr",
+ ...
+ }
+ }
+},
+"serve": {
+ ...
+ "configurations": {
+ ...
+ "fr": {
+ "browserTarget": "angular.io-example:build:fr"
+ }
}
}
```
-You then pass the configuration with the `ng serve` or `ng build` commands.
-The example below shows how to serve the French language file created in previous
+You then pass the configuration with the `ng serve` or `ng build` commands.
+The example below shows how to serve the French language file created in previous
sections of this guide:
ng serve --configuration=fr
-For production builds, you define a separate `production-fr` build configuration in
+For production builds, you define a separate `production-fr` build configuration in
your `angular.json`.
```