> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/platform/platform/core-services/localization-service/configuring-localization/setup-base-product-localisation.md).

# Setup Base Product Localisation

## Overview <a href="#overview" id="overview"></a>

DIGIT supports multiple languages. To enable this feature begin with setting up the base product localisation. The multilingual UI support makes it easier for users to understand the DIGIT operations.

## Pre-requisites <a href="#pre-requisites" id="pre-requisites"></a>

Before you proceed with the configuration, make sure the following pre-requisites are met -

* Before starting the localisation setup one should know the React and eGov FrameWork.
* Before setting up localisation, make sure that all the keys are pushed to the Create API and also get prepared with the values that need to be added to the Localisation key specific to particular languages that are being added to the product.
* Make sure you know where to add the localisation in the code.

## Key Functionalities <a href="#key-functionalities" id="key-functionalities"></a>

After localisation, users can view DIGIT screens in their preferred language. Completing the application is simple as the DIGIT UI allows easy language selection.

## Deployment Details <a href="#deployment-details" id="deployment-details"></a>

* Once the key is added to the code as per requirement, the deployment can be done in the same way as the code is deployed.

## Configuration Details <a href="#configuration-details" id="configuration-details"></a>

* Select a label that needs to be localised from the Product code. Here is the example code for a header before setting up Localisation.

<div align="left"><figure><img src="/files/KQlQx0DWxoMgAVjJkh1c" alt=""><figcaption></figcaption></figure></div>

* As we see the above which supports only the English language, To set up Localisation to that header we need to the code in the following manner.

<div align="left"><figure><img src="/files/a59WsLuZHGN3rPkwh5OV" alt=""><figcaption></figcaption></figure></div>

* When comparing the code before and after the Localisation setup, we can see that the following code has been added.

{

labelName: "Trade Unit ",

labelKey: "TL\_NEW\_TRADE\_DETAILS\_TRADE\_UNIT\_HEADER"

},

* The values here can be added to the key using two methods: either via the newly developed localisation screen or by updating the key values through the Postman application to create an API.

## Reference Docs <a href="#reference-docs" id="reference-docs"></a>

#### Doc Links <a href="#doc-links" id="doc-links"></a>

| Title                                                                                                             | Link                                                                                                                                                                |
| ----------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Adding new language to the DIGIT System. Refer to the link provided to find out how languages are added in DIGIT. | [Adding New Language](https://urban.digit.org/setup/configure-digit/configuring-digit-services/configuring-common-services/setting-up-a-language/adding-a-language) |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digit.org/platform/platform/core-services/localization-service/configuring-localization/setup-base-product-localisation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.