> For the complete documentation index, see [llms.txt](https://brunx-mods.gitbook.io/brunx-mods-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://brunx-mods.gitbook.io/brunx-mods-docs/products/scripts/cinema-system/configuration/language.md).

# Language

It is possible to create or use existing languages within **our script** by accessing the file located at `brnx-cinemasystem/modules/locales`. In this file, you can define translations for the desired language. To select the language to be used, simply configure the `config.locale` variable in the `brnx-cinemasystem/modules/shared/config.lua` file, as shown in the example below.

{% code title="brnx-cinemasystem/modules/shared/config.lua" %}

```lua
config.locale = 'en'
```

{% endcode %}

{% hint style="warning" %}
If you wish to create a new language, make sure to follow the structure of other example files. The `.json` file format should remain the same, but with translations adapted to the new language. See the example below:
{% endhint %}

{% code title="brnx-cinemasystem/modules/locales/jp.json" %}

```json
// JAPANESE
{
  "CURRENCY": "JPY",
  "PANEL": {
    "FRONT_END": {
      "CINEMAS": "シネマ",
      "EDIT_FILM": "映画を編集",
      "CREATE_FILM": "映画を作成",
      "ADD_FILM": "映画を追加",
      "NAME_FILM": "映画タイトル：",
      "MINUTES_FILM": "上映時間（分）：",
      "IMG_FILM": "画像（URL）：",
      "SYNOPSIS_FILM": "あらすじ：",
      "SCHEDULES_FILM": "上映スケジュール：",
      "PRICE_FILM": "価格：",
      "PLATFORM_FILM": "プラットフォーム：",
      "URL_FILM": "動画（URL）：",
      "REQUIRED_FIELD": "必須項目です。",
      "DELETE": "削除",
      "EDIT": "編集",
      "CONFIRM": "確認",
      "CANCEL": "キャンセル",
      "SAVE": "保存",
      "DELETE_FILM": "映画「{film}」を削除してもよろしいですか？すべてのセッションが終了し、更新を適用するために再起動されます。",
      "SAVE_FILM": "映画を保存してもよろしいですか？すべてのセッションが終了し、更新を適用するために再起動されます。"
    }
  },
  "TABLET": {
    "FRONT_END": {
      "LOADING": "読み込み中...",
      "PURCHASE_HISTORY": "購入履歴",
      "SELECT_A_TIME": "時間を選択",
      "NO_FILM": "現在、利用可能な映画はありません。",
      "BUY_TICKET": "{name} のチケットを {time} に {price} で購入しますか？",
      "CONFIRM": "確認",
      "CANCEL": "キャンセル",
      "ORDER": "注文",
      "PRODUCT": "商品",
      "VALUE": "金額",
      "DATE": "日付"
    }
  },
  "NOTIFYS": {
    "NO_SPACE": "リュックのスペースがありません。",
    "PURCHASE_ITEM": "{name} を {price} で1つ購入しました。",
    "NO_PURCHASE_ITEM": "この商品を購入するのに十分なお金がありません。",
    "FINISHED": "セッションが終了しました。",
    "HAS_TICKET": "このチケットはすでに購入済みです。",
    "NO_PURCHASE_TICKET": "チケットを購入するのに十分なお金がありません。",
    "PURCHASE_TICKET": "映画 {name} のチケットを {hour}時、ルーム {room} にて {price} で購入しました。",
    "NO_TICKET": "このセッションのチケットをまだ持っていません。",
    "NO_SESSION": "セッションはまだ開始されていません。スケジュール一覧：{schedules}。現在時刻：{currentTime}。"
  }
}

```

{% endcode %}


---

# 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://brunx-mods.gitbook.io/brunx-mods-docs/products/scripts/cinema-system/configuration/language.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.