Me
Based on these criteria: Names the doc(s)you drew from and clearly cite them.
Preserves visuals: includes at least one relevant image/screenshot from the doc.
Preserves links: any in-page or cross-doc links are present and correctly formatted.
Lists key fields with short explanations, defaults, and any validation rules (required/optional).
Mentions limits (size, file type, counts, rate limits) if the feature has them.
State what’s not covered if the needed info isn’t in the KB page, without referencing “chunks”.
Formatting: clear headings/bullets/tables; no jargon unexplained; no hallucinations. Explain how to manage localisations. Where can I mange them
Enki
# Managing Localisations in Harmony
This information comes from **Managing Localisations in Harmony**.
## Overview
Localisation is the process of translating and adapting your game's content to specific markets. It goes beyond simple translation—it includes adapting dates, currencies, and general content for different audiences. Through Harmony, you can centrally manage all your game's localisations.
## How to Access Localisation Management
1. Access Harmony at:
- **Staging**: https://harmony-staging.tripledotapi.com/admin
- **Production**: https://harmony.tripledotapi.com/admin
2. Click your game from the home page
3. On the left sidebar, click the **Localisations** dropdown menu
## Localisation Management Sections
Once you expand Localisations, you'll find four management areas:
| Section | Purpose |
|---------|---------|
| **Languages** | View and add languages available for translation in your game (English is the source language and cannot be deleted) |
| **Translations (Test)** | Upload, edit, and test translations in a test environment before going live |
| **Translations (Live)** | Read-only view of translations currently in production |
| **AI Translations** | Use AI assistance to automate translation of key text fields |
## Managing Languages
### Adding a New Language
1. In the **Languages** section, click the **[New]** button in the upper right
2. Select your language from the dropdown list (you can search by name or language code)
3. Click **[Save]**
The **In Use** column shows which configurations use each language.
## Managing Translations (Test)
The **Translations (Test)** section allows you to create, edit, and test translations before pushing them to production.
### Adding New Translations
You have four options:
1. **Manually** - Add individual keys one at a time
2. **Via CSV upload** - Bulk upload translations
3. **With AI Assistance** - Auto-generate translations
4. **Via Internal API** - Programmatic integration
#### Adding Translations Manually
1. Click **[Add Key]**
2. Enter a unique name for your key, select the content type, and add a description
3. Type the English source text under **English EN**
4. Click **[Add]**
5. In the **Changed Keys** table that appears, add translations manually (changes highlight in yellow)
6. Click **[Save]**
#### Uploading Translations via CSV
1. Click **[Upload CSV]**
2. Upload your file
**CSV Format Requirements:**
- Must include: Key, Type, Desc (description - can be empty), and language codes (ISO-639-1 format, e.g., `en`, `pt-BR`)
- File must be UTF-8 encoded
- Any new languages must be created in the Languages section first
- Remove any quotation marks Excel/Google Sheets may add to the beginning
- The **[CSV Upload]** button requires at least one manual change beforehand to be enabled
**Validation**: If there are errors, use the **Show only keys with validation errors** checkbox to see and fix them (marked in red).
### Editing Translations
1. Double-click the text you want to edit
2. Make changes (highlighted in green in a new table above)
3. Click **[Save]** to apply changes to the test environment
4. To push changes to production, click **[Review Difference]** and then **[Apply to Live]**
### Deleting and Undoing Changes
- Use the **yellow undo button** to undo edited keys you don't want to apply to live
- Use the **red trash icon** to delete keys
- Use the **undo button** to recover accidentally deleted keys
### Downloading Translations
Click **[Download]** in the **Translations (Test)** section to export translations in CSV format.
## Using AI for Translations
### Generating AI Translations
1. In **Translations (Test)**, click **[Download with AI]**
2. Select your target languages
3. Click **[Confirm]**
The system will generate translations shortly, and you'll see a success message.
### Accessing AI Translation History
1. Go to **Localisations > AI Translations** in the sidebar
2. View all AI-generated translations with their status
3. Track progress of pending requests
### Downloading AI-Generated Translations
1. Locate the file in the AI Translations table
2. If status is "Generated", click the **Download** button
3. The CSV file uses the same format as the regular download/upload feature
**Alternative Download Method**: If the download doesn't work, right-click the **Download** button and select **Save Link As...** to save the file locally.
### Deleting AI Translation Files
1. In the AI Translations table, locate the file
2. If status is "Generated", "Scheduled", or "Failed", the delete button is available
3. Click the **delete** icon and confirm
## Applying Translations to Production (Live)
Localisation follows a test-first workflow for quality assurance:
1. In **Translations (Test)**, click **[Review Difference]** to see all changes since the last production push
2. The last push date appears in the upper right
3. Review the changes (new keys are marked in green)
4. Click **[Apply to Live]** to push to production
5. You'll be redirected to **Translations (Live)**, a read-only view of production content
**Note**: Any deleted keys will also be removed during this process. If there are no differences between test and live, you'll receive a notification.
## Settings Configs (Game Server)
In **Game Server > Settings Configs**, you can create localisation configurations that control language settings for your game.
### Creating a New Config
1. Click **[+New]** in the upper left
2. Enter a config name
3. Select supported languages and add them using the dropdown
4. Set the **Client Default Language** (the language shown when players open the game)
5. Optionally configure a language selection popup and reorder languages via drag-and-drop
6. Click **[Save]**
Once created, you can use your config in Base Config, Overrides, or A/B Experiments by enabling the field and selecting your config.
## Syncing Localisations with Hawk
Some Hawk features (like Campaigns and App Links) can be localised. Hawk syncs with localisations **every hour automatically**.
### Manual Synchronisation
1. Add keys to the Localisation App first
2. Go to **Hawk > Localisations**
3. Click **[Synchronize]** to force an immediate sync
4. Once synced, keys are available in any Hawk feature that supports localisation
## Using the Localisation API
For programmatic integration, you can use the Internal API:
1. Authenticate with your personal SSO token ([get this from your SSO Server profile](/wiki/spaces/KB/pages/3292790799/Generating+SSO+User+Tokens))
2. Obtain your `app_id` (unique game identifier) - [see Public App IDs](/wiki/spaces/GS/pages/3122561158/Public+App+IDs)
3. Use the endpoint: https://backstage.tripledotapi.com/catalog/localisations-server/api/internal/definition
## Related Documentation
- [Rules in Game Server](https://tripledotstudios.atlassian.net/wiki/spaces/KB/pages/2668494860)
- [Game Settings Configuration](https://tripledotstudios.atlassian.net/wiki/spaces/KB/pages/2580021328)
- [Setting up A/B Experiments](https://tripledotstudios.atlassian.net/wiki/spaces/KB/pages/2581889051)