---
title: "Language Management (i18n Localization)"
description: "Documentation for Language Management"
---
## Table of Contents
1. [Overview & Localization Architecture](#1-overview--localization-architecture)
2. [Business & Operational Significance](#2-business--operational-significance)
3. [π― User Roles & Key Capabilities](#3--user-roles--key-capabilities)
4. [Visual Interface & Layout](#4-visual-interface--layout)
5. [Field Reference & Language Catalog Parameters](#5-field-reference--language-catalog-parameters)
6. [Localization Standards & React i18n Mechanics](#6-localization-standards--react-i18n-mechanics)
7. [AI-Assisted Translation Automation](#7-ai-assisted-translation-automation)
8. [Troubleshooting & Verification](#8-troubleshooting--verification)
9. [Model Context Protocol (MCP) AI Integration](#9-model-context-protocol-mcp-ai-integration)
10. [Glossary](#10-glossary)
---
## 1. Overview & Localization Architecture
In **Ring2All SBC**, the **Language Management** module centralizes internationalization (i18n) governance, translation catalog maintenance, and localization telemetry across the web interface. Built on modern client-side translation frameworks (`react-i18next`), the platform enforces **English (`en`) as the canonical base language** with 100% key coverage, paired with complete **Spanish (`es`)** localization for Latin American and European operations.
```
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β React Frontend i18n Engine β
β (useI18n Hook) β
ββββββββββββββββββββββββββββββββ¬βββββββββββββββββββββββββββββββ
β
Resolve User Locale Preference
(Browser Locale / User Profile Setting)
β
ββββββββββββββββββββββ΄βββββββββββββββββββββ
β β
βββββββββββΌββββββββββββ βββββββββββΌββββββββββββ
β English (en) β β Spanish (es) β
β Canonical 100% Keys β β Full Regional Local β
β β’ "Engine Settings" β β β’ "Ajustes Motor" β
β β’ "Role Profiles" β β β’ "Perfiles de Rol" β
βββββββββββββββββββββββ βββββββββββββββββββββββ
β β
ββββββββββββββββββββββ¬βββββββββββββββββββββ
β
βΌ
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β Fallback Resolution Strategy β
β If key is missing in target locale -> Render English Base β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
```
The system includes real-time translation completion tracking, translation coverage percentage badges, and integrated AI translation triggers that translate missing technical telecom strings while preserving syntax tokens and variable interpolation tags.
---
## 2. Business & Operational Significance
* **Global Workforce Enablement**: Provides regional Network Operations Centers (NOCs) and field engineers with a fully localized, native-language user interface, minimizing misunderstandings during emergency network triage.
* **Reduction in Operator Configuration Errors**: Clear, idiomatically accurate technical translations prevent misunderstandings of critical telecom directives (such as SIP header manipulation or anti-flood ban thresholds).
* **Guaranteed Zero-Broken-Key Experience**: Through hierarchical fallback resolution, if a new feature is deployed with partial translation, the interface gracefully displays the canonical English string rather than an ugly raw translation key (e.g., `sbc.routing.carrier_error`).
* **Automated AI Translation Acceleration**: Reduces internationalization rollout cycles from weeks to seconds by leveraging enterprise LLMs to translate technical telecom terminology contextually.
---
## 3. π― User Roles & Key Capabilities
| Role | Primary Use Case | Key Capabilities |
| :--- | :--- | :--- |
| **Localization & i18n Lead** | Platform Translation Quality | Audit translation coverage percentages, inspect missing translation strings, and approve localized terms. |
| **SBC Operations Manager** | Regional Workforce Provisioning | Set default interface languages for regional teams and ensure operational glossaries match telecom standards. |
| **Multi-Regional Support Specialist** | Operator Interface Verification | Test localized UI layouts for text truncation, overflow issues, and RTL/LTR script rendering. |
| **Systems Administrator** | Language Catalog Governance | Trigger AI batch translations for newly added modules and export translation JSON catalogs. |
| **AI Platform Copilot / Administration Agent** | Automated Localization Telemetry & Translation Inspection | Programmatically list system languages, audit translation namespace coverage, and inspect localization key counts via MCP. |
---
## 4. Visual Interface & Layout
The Language Management view presents a catalog of supported system languages, displaying ISO codes, total key counts, completion percentages, and automated translation triggers.
---
## 5. Field Reference & Language Catalog Parameters
| Field Name | Type | Format / Options | Description |
| :--- | :--- | :--- | :--- |
| **Language Name** | String | Text (e.g., `English (US)`, `EspaΓ±ol (ES)`) | Display name of the language presented in profile appearance selectors. |
| **ISO Code** | String | ISO 639-1 (e.g., `en`, `es`, `fr`) | Standard two-letter international language identifier. |
| **Total Keys** | Counter | Integer (e.g., `1,420`) | The total count of registered translation keys defined across all platform modules. |
| **Completed Keys** | Counter | Integer (e.g., `1,420`) | The count of keys that have valid localized strings in this specific language catalog. |
| **Coverage Percentage**| Badge | Percentage (`100%`) | Visual indicator of localization completeness (`100%` Green, `90-99%` Blue, `<90%` Amber). |
| **Operational Status** | Switch | `Active` / `Disabled` | Enables or disables the language in the user's global language switcher dropdown. |
| **AI Translate Action** | Button | Action trigger | Triggers the AI translation engine to automatically populate missing or untranslated keys. |
---
## 6. Localization Standards & React i18n Mechanics
Ring2All SBC follows strict software engineering rules for internationalization:
### 6.1 Clean Component Translation
All user-facing text, error messages, form labels, and table headers are wrapped in translation hooks:
```typescript
import { useI18n } from '@/hooks/useI18n';
export function CarrierHeader() {
const { t } = useI18n();
return (
);
}
```
### 6.2 Pure UTF-8 Encoding Standard
All language JSON files (`en.json`, `es.json`) are stored strictly in clean UTF-8 without legacy Windows-1252 or corrupted byte sequences. Punctuation uses standardized Unicode glyphs (`β’`, `βΉ`, `β`).
---
## 7. AI-Assisted Translation Automation
When a new platform feature introduces hundreds of new strings, administrators can click the **AI Translate** button:
```text
[Source: English Dictionary] βββΊ [Prompt with Telecom System Context] βββΊ [LLM Engine]
"Longest Prefix Match (LPM)" β
"Anti-flood ban threshold" βΌ
[Output: Spanish Dictionary]
"Coincidencia de prefijo mΓ‘s largo (LPM)"
"Umbral de bloqueo anti-flood"
```
1. **Context-Aware Telecom Translation**: The AI engine is primed with a specialized softswitch glossary ensuring that terms like *"Trunk"*, *"Carrier"*, *"Register"*, and *"Drop"* are translated into their correct telecommunications equivalents rather than generic literal translations.
2. **Token Preservation**: Variable placeholders (e.g., `{{count}}`, `{{seconds}}`, ``) are preserved with 100% fidelity.
---
## 8. Troubleshooting & Verification
### Inspecting Active Language Preference in Browser
Open the browser developer tools console to verify the active language setting:
```javascript
console.log('Current Locale:', localStorage.getItem('i18nextLng'));
```
### Validating JSON Catalog Integrity on Disk
On the SBC web server, verify that translation files contain valid JSON syntax:
```bash
python3 -m json.tool /var/www/sbc-web/dist/locales/en.json > /dev/null && echo "English JSON valid"
python3 -m json.tool /var/www/sbc-web/dist/locales/es.json > /dev/null && echo "Spanish JSON valid"
```
---
## 9. Model Context Protocol (MCP) AI Integration
Ring2All SBC exposes dedicated Model Context Protocol (MCP) tools enabling AI agents, autonomous NOC bots, and administrative copilot assistants to query system localization catalogs and monitor translation namespace statistics.
### Available MCP Tools
| Tool Name | Operation | Risk Level | Description |
| :--- | :--- | :--- | :--- |
| `list_sbc_languages` | Read | Low (`read`) | List supported SBC localization languages (English, Spanish) and their operational translation statuses. |
| `get_sbc_language_stats` | Read | Low (`read`) | Get translation key count, namespace coverage, and completion statistics for a specific language code (e.g., `en`, `es`). |
### Tool Schemas & Parameter Definitions
#### `list_sbc_languages`
```json
{
"name": "list_sbc_languages",
"description": "List supported SBC localization languages (English, Spanish) and their translation status.",
"inputSchema": {
"type": "object",
"properties": {}
}
}
```
#### `get_sbc_language_stats`
```json
{
"name": "get_sbc_language_stats",
"description": "Get translation key count, namespace coverage, and completion statistics for a specific language code (e.g. en, es).",
"inputSchema": {
"type": "object",
"properties": {
"languageCode": {
"type": "string",
"description": "ISO-639-1 language code (en, es)"
}
},
"required": ["languageCode"]
}
}
```
### Realistic Payload Examples
#### Query Request (`get_sbc_language_stats`)
```json
{
"languageCode": "es"
}
```
#### Successful Response (`get_sbc_language_stats`)
```json
{
"success": true,
"data": {
"languageCode": "es",
"namespacesCount": 8,
"totalKeys": 1284,
"namespaces": {
"routing": 240,
"reports": 180,
"security": 165,
"technology": 195,
"logic": 140,
"tools": 110,
"admin": 194,
"common": 60
}
}
}
```
### Natural Language Prompt Scenarios
#### English (Localization Coverage Audit)
> *"Check the localization statistics for Spanish ('es') on Ring2All SBC and verify which namespaces have translation keys loaded."*
#### Spanish (InspecciΓ³n de Idiomas del Sistema)
> *"Lista todos los idiomas disponibles en el SBC y comprueba si el catΓ‘logo en espaΓ±ol tiene paridad de claves con el idioma base en inglΓ©s."*
### Enterprise AI Safety Guardrails
* **Disk-Level Read Isolation**: MCP language tools access physical i18n JSON files in read-only mode, guaranteeing that live translation namespaces cannot be corrupted by autonomous agents.
* **Fallback Preserved**: Translation queries always reference the canonical English base directory if target files or keys are missing.
---
## 10. Glossary
* **i18n (Internationalization)**: The design and engineering process of designing an application so that it can be adapted to various languages and regions without engineering changes.
* **ISO 639-1**: A standardized international nomenclature used to classify languages with two-letter lowercase identifiers (e.g., `en`, `es`, `fr`, `de`).
* **Fallback Resolution**: A software mechanism that supplies a default string from a primary language when a translation is missing in the user's selected language.
* **Variable Interpolation**: Dynamically injecting runtime values (such as usernames or call counts) into localized text templates.