> For the complete documentation index, see [llms.txt](https://docs.swingsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.swingsoftware.com/integrator-for-notes/how-to/how-to-apply-multilingual-support.md).

# How to apply multilingual support

## Description

Let's say you want to have English and Norwegian messages versions.

## Solution

If you need multilingual support, you should modify “SW\_IntOfficeMsg” function in the “SwIntfOfficeMsg” library.

Basically, we are using this function in our code to get all the messages defined in the "(Declarations)" section.

 Here is an example on how to enable multilingual support.

* In the “SwIntOfficeMsg” library (or anywhere else, where appropriate) create a global variable named, say, SwLanguage
* This variable could be set to either "EN" or "NO"
* Now, in the “SwIntOfficeMsg” library "(Declarations)" section rename all the constants to SW\_IntOfficeMsgEN1,2, etc. and create new ones, named SW\_IntOfficeMsgNO1,2, etc.
* The next step would be to modify SW\_IntOfficeMsg function. You will have something like this:

```
Function SW_IntOfficeMsg (MsgNo As Integer) As String
Select Case MsgNo
Case 1
    If SwLanguage = "EN" Then
        SW_IntOfficeMsg = SW_IntOfficeMsgEN1
    Else
        SW_IntOfficeMsg = SW_IntOfficeMsgNO1
    End If
Case 2
    If SwLanguage = "EN" Then
        SW_IntOfficeMsg = SW_IntOfficeMsgEN2
    Else
        SW_IntOfficeMsg = SW_IntOfficeMsgNO2
    End If
```


---

# 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://docs.swingsoftware.com/integrator-for-notes/how-to/how-to-apply-multilingual-support.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.