Step 4 - Configure Language Mappings
It is important to ensure that the language mappings are accurate between AEM and Trados. You must make sure the correct language code is selected. For example, if Trados expects en_us > es, then AEM users must select the correct language codes during translation project creation.
Language mapping nodes are installed as part of the connector, but are visible only on dev and staging environments within CRXDE Lite - /apps/sdl-connector/config/languageMapping. The in node on the left is the AEM language code, while the languageMapping value under Properties is the language code that should be present at RWS level.

On production environments, Adobe does not allow access to CRXDE Lite.
On production environments, Adobe does not allow access to CRXDE Lite.
To change one or more language codes used in AEM, administrator users will have access to the Trados UI to upload a new language mapping.

The language mapping to be uploaded is a standard comma-separated CSV file with three columns: Language code (indicating the AEM language node), Language mapping (indicating the supported RWS language code), and Language name (indicating the language that will be displayed in the Trados UI).

RWS can provide you with the standard language mapping file for Trados environments; you can update it by changing or adding new entries. After the upload, the language mapping will be updated and an automated listener service will apply it.
The language mapping to be uploaded is a standard comma-separated CSV file with three columns: Language code (indicating the AEM language node), Language mapping (indicating the supported RWS language code), and Language name (indicating the language that will be displayed in the Trados UI).
RWS can provide you with the standard language mapping file for Trados environments; you can update it by changing or adding new entries. After the upload, the language mapping will be updated and an automated listener service will apply it.