You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory-b2c/localization.md
+5-157Lines changed: 5 additions & 157 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ manager: celestedg
8
8
ms.service: active-directory
9
9
ms.workload: identity
10
10
ms.topic: reference
11
-
ms.date: 03/09/2020
11
+
ms.date: 03/11/2020
12
12
ms.author: mimart
13
13
ms.subservice: B2C
14
14
---
@@ -203,161 +203,9 @@ Under the **BuildingBlocks** element, add the **Localization** element with the
203
203
</Localization>
204
204
```
205
205
206
-
### Provide language-specific strings and collections
206
+
##Next steps
207
207
208
-
Add **LocalizedResources** elements inside the **Localization** element after the close of the **SupportedLanguages** element. You add **LocalizedResources** elements for each page (content definition) and any language you want to support. To customize the unified sign-up or sign-in page, sign-up and multi-factor authentication (MFA) pages for English, Spanish, and France, you add the following **LocalizedResources** elements.
209
-
210
-
- Unified sign-up or sign-in page, English `<LocalizedResources Id="api.signuporsignin.en">`
211
-
- Unified sign-up or sign-in page, Spanish `<LocalizedResources Id="api.signuporsignin.es">`
212
-
- Unified sign-up or sign-in page, France `<LocalizedResources Id="api.signuporsignin.fr">`
213
-
- Sign-Up, English `<LocalizedResources Id="api.localaccountsignup.en">`
- MFA, France `<LocalizedResources Id="api.phonefactor.fr">`
219
-
220
-
Each **LocalizedResources** element contains all of the required **LocalizedStrings** elements with multiple **LocalizedString** elements and **LocalizedCollections** elements with multiple **LocalizedCollection** elements. The following example adds the sign-up page English localization:
221
-
222
-
Note: This example makes a reference to `Gender` and `City` claim types. To use this example, make sure you define those claims. For more information, see [ClaimsSchema](claimsschema.md).
<LocalizedStringElementType="ClaimType"ElementId="email"StringId="UserHelpText">Please enter your email</LocalizedString>
242
-
<LocalizedStringElementType="ClaimType"ElementId="email"StringId="PatternHelpText">Please enter a valid email address</LocalizedString>
243
-
<LocalizedStringElementType="UxElement"StringId="button_continue">Create new account</LocalizedString>
244
-
<LocalizedStringElementType="ErrorMessage"StringId="UserMessageIfClaimsPrincipalAlreadyExists">The account you are trying to create already exists, please sign-in.</LocalizedString>
<LocalizedStringElementType="ClaimType"ElementId="email"StringId="DisplayName">Dirección de correo electrónico</LocalizedString>
268
-
<LocalizedStringElementType="ClaimType"ElementId="email"StringId="UserHelpText">Dirección de correo electrónico que puede usarse para ponerse en contacto con usted.</LocalizedString>
269
-
<LocalizedStringElementType="ClaimType"ElementId="email"StringId="PatternHelpText">Introduzca una dirección de correo electrónico.</LocalizedString>
<LocalizedStringElementType="ErrorMessage"StringId="UserMessageIfClaimsPrincipalAlreadyExists">Ya existe un usuario con el id. especificado. Elija otro diferente.</LocalizedString>
272
-
</LocalizedStrings>
273
-
</LocalizedResources>
274
-
```
275
-
276
-
### Edit the ContentDefinition for the page
277
-
278
-
For each page that you want to localize, specify the language codes to look for in the **ContentDefinition**.
279
-
280
-
In the following example, English (en) and Spanish (es) custom strings are added to the sign-up page. The **LocalizedResourcesReferenceId** for each **LocalizedResourcesReference** is the same as their locale, but you could use any string as the identifier. For each language and page combination, you point to the corresponding **LocalizedResources** you previously created.
<LocalizedStringElementType="ClaimType"ElementId="email"StringId="UserHelpText">Please enter your email</LocalizedString>
332
-
<LocalizedStringElementType="ClaimType"ElementId="email"StringId="PatternHelpText">Please enter a valid email address</LocalizedString>
333
-
<LocalizedStringElementType="UxElement"StringId="button_continue">Create new account</LocalizedString>
334
-
<LocalizedStringElementType="ErrorMessage"StringId="UserMessageIfClaimsPrincipalAlreadyExists">The account you are trying to create already exists, please sign-in.</LocalizedString>
<LocalizedStringElementType="ClaimType"ElementId="email"StringId="DisplayName">Dirección de correo electrónico</LocalizedString>
353
-
<LocalizedStringElementType="ClaimType"ElementId="email"StringId="UserHelpText">Dirección de correo electrónico que puede usarse para ponerse en contacto con usted.</LocalizedString>
354
-
<LocalizedStringElementType="ClaimType"ElementId="email"StringId="PatternHelpText">Introduzca una dirección de correo electrónico.</LocalizedString>
<LocalizedStringElementType="ErrorMessage"StringId="UserMessageIfClaimsPrincipalAlreadyExists">Ya existe un usuario con el id. especificado. Elija otro diferente.</LocalizedString>
357
-
</LocalizedStrings>
358
-
</LocalizedResources>
359
-
<!-- More localized resources... -->
360
-
</Localization>
361
-
</BuildingBlocks>
362
-
```
208
+
See the following article, for example of using localiztion:
363
209
210
+
-[Language customization with custom policy in Azure Active Directory B2C](custom-policy-localization.md)
211
+
-[Language customization with user flows in Azure Active Directory B2C](user-flow-language-customization.md)
0 commit comments