How localization of adaptive form works
When an adaptive form is rendered, it identifies the requested locale by looking at the following parameters in the specified order:
-
Request parameter
afAcceptLang
To override the browser locale of users, you can pass the
afAcceptLang
request parameter to force the locale. For example, the following URL will force to render the form in Japanese locale:https://[*server*]:[*port*]/<*contextPath*>/<*formFolder*>/<*formName*>.html?wcmmode=disabled&afAcceptLang=ja
-
The browser locale set for the user, which is specified in the request using the
Accept-Language
header. -
Language setting of the user specified in AEM.
Once the locale is identified, the adaptive forms picks the form-specific dictionary. If the form-specific dictionary for the requested locale is not found, it uses the English (en) dictionary is used.
If a client library for the requested locale doesn’t exist, it checks for a client library for the language code present in the locale. For example, if the requested locale is en_ZA
(South African English) and the client library for en_ZA
doesn’t exist, the adaptive form will use the client library for en
(English) language, if it exists. However, if none of them exist, the adaptive form uses the dictionary for en
locale.