> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/multi-language-and-text-tagging-support/multi-language-support-and-text-tagging-overview.md).

# Multi-Language Support and Text Tagging Overview

Multi-Language Support (MLS) allows you to create one application but make it available to users in multiple languages. You enable MLS translations and Text Tagging in the project settings configuration, and these features use the same functionality to allow you to manage texts across multiple languages and in multiple UI locations in the project. For more detailed information, click [here](/release-9/platform-documentation/multi-language-and-text-tagging-support.md).

## Introduction to Multi-Language Support

LogicNets supports the display of logicnets and support content in multiple languages through the MLS functionality. You can activate MLS for new and existing logicnets content as well as in the Knowledge Center, making it possible for applications to be deployed to users in multiple languages.

MLS is not a translation system and content owners must provide and maintain accurate content translations, but the MLS functionality provides the ability to standardize how the translated content displays to users. English is the base language of all MLS-based application user content and resources and, with the MLS functionality enabled, the system displays translated versions words, phrases, and captions in other languages.

Applications using the Multi-Language Support functionality assign a unique, system-generated translation key to each word or phrase that the application displays to users. The system then stores these keys in language-specific data tables that also contain the translated versions of each of the words; for example, in an application that provides a Dutch translation there will be a table that identifies a translation key and the associated phrase in Dutch.

As you add words or phrases to an application the system updates the translation key table. When you begin to type content in a node the system displays an autocomplete field that displays similar words or phrases that already exist in the application. If you click on the displayed option the system adds it and the associated translation key into the node. If you add a caption that is not already in the database the system assigns it a translation key and add it to the data tables. After creating an application, you can export the translation tables, translate the content or send it to be translated, and then import the translations.

## Text Tagging

LogicNets extended the MLS features to efficiently manage large and repeated sets of end-user communication regardless of language. By re-using the same GUID for repeated text, when you update one occurrence, the system updates all other occurrences with the same text with the same GUID. The system gives you the option to confirm the update or create a new GUID.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://community-test.logicnets.com/release-9/platform-documentation/multi-language-and-text-tagging-support/multi-language-support-and-text-tagging-overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.