---
title: "Language Translation"
slug: "language-translation"
description: "This article will cover the steps required to add a language to Autoform DM. This is currently only available via manual translation and configuration."
tags: ["Translation", "Language", "General information", "Autoform DM"]
updated: 2024-10-16T08:19:42Z
published: 2024-10-16T08:19:42Z
canonical: "kb.lasernetgroup.com/language-translation"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.lasernetgroup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Language Translation

This article will cover the steps required to add a language to Autoform DM.

This is currently only available via manual translation and configuration, as Autoform DM is only shipped with an English language set. Anyone implementing support for another language will be required to do their own translations.

## Identify Locale

Identify the locale code for the specific language required. For example, if you want to provide a German translation, the locale would be **De**. A list of locale codes can be found at [https://developer.chrome.com/webstore/i18n#localeTable](https://developer.chrome.com/docs/extensions/reference/api/i18n#concepts_and_usage).

For the rest of this guide, we will refer to locale **De**; however, wherever you see this locale, you should substitute it with your required locale.

## Translate Files

You will need to provide file translations for each of the .properties files containing display text.

The files within `pdm_app_module.ear` that should be translated are:

```plaintext
logging-service-*.jar/pdm-logging.properties
system-reporting-*.jar/ApplicationResources.properties
web-common-*.jar/ImportDocumentApplicationResources.properties
web-*.war/applet/DocImport.jar/AppletResources.properties
web-*.war/WEB-INF/classes/ApplicationResources.properties
web-*.war/WEB-INF/classes/pdm-logging.properties
web-integrations-*.war/applet/DocImport.jar/AppletResources.properties
web-integrations-*.war/WEB-INF/classes/ApplicationResources.properties
```

In order to translate the files, you must:

1. Make a copy of the original .properties file.
2. Rename the copy with your desired locale using the format: <resource_name>_<locale>.properties, for example, ApplicationResources_de.properties.
3. Translate the copy as desired
4. Add the copy to the .ear file alongside the original.

> [!NOTE]
> Note:
> 
> When translating the .properties file, ensure the format <property.name>=<property.value> is used. You only need to translate the property values, not the property names.

For example, when translating into German:

`login.username=Username login.password=Password`

Becomes:

`login.username=Benutzername login.password=Passwort`

## Update Server Locale

For Autoform DM to configure the changes, the server it is running on must be configured with the desired locale.

On Windows, follow these steps:

1. Navigate to **Region & Language Settings**.
2. Set your **Country or region** to the correct region, for example, **Germany**.
3. Add a language for that region, for example, **Deutsch (Deutschland)**, and set it as the default.

When you next restart Autoform DM, the regions should be configured correctly for the server and display the correct language.