# Smart Localization Suite Changelog

{% updates format="full" %}
{% update date="2026-01-20" %}

## Version 2.0.0

Breaking release introducing a fully key-based localization architecture.

This version replaces the legacy component-based workflow with a centralized, production-grade table system designed for scalability and long-term maintainability.

<details>

<summary>Breaking Changes</summary>

* Removed legacy `LocalizedTMP` component.
* Deprecated component-based localization workflow.
* All localization now requires keys defined inside `LocalizationTable`.

</details>

<details>

<summary>New Features</summary>

* 100% key-based localization system.
* `LocalizationTable` as the single source of truth.
* New `LocalizedTMPKeyed` binding component.
* Editor translation pipeline operating strictly by key.
* One-click full project migration (Lite → Suite), including scenes and prefabs.
* Unified dashboard and inspector workflow aligned with the new architecture.

</details>

<details>

<summary>Improved</summary>

* Cleaner and safer Editor architecture.
* Removal of dual-system logic and legacy code paths.
* Deterministic migration process.
* Improved internal consistency between runtime and Editor systems.

</details>

<details>

<summary>Fixed</summary>

* Structural inconsistencies caused by legacy component workflows.

</details>
{% endupdate %}

{% update date="2025-09-20" %}

## Version 1.0.0

Initial release of Smart Localization Suite, providing a centralized localization workflow with multi-provider translation support.

<details>

<summary>New Features</summary>

* Project Settings integration for global localization configuration.
* Language management with add, remove, and sorting capabilities.
* Provider selection supporting:
  * MyMemory
  * Google
  * DeepL
  * Azure
  * Amazon
  * IBM Watson
  * Yandex
  * LibreTranslate
  * Smartling
* `LocalizedTMP` component for binding translations to TextMeshPro objects.
* Inspector workflow including Translate button, filtering options, and status badges.
* Placeholder validation for cross-language consistency.
* Localization Dashboard with matrix view of all entries and languages.
* Inline editing of translations directly from the dashboard.
* MyMemory quota tracking with daily usage monitoring.
* Security guard system to keep API keys restricted to Editor-only assets.
* Diagnostics utilities (scene refresh, global apply tools).
* Editor-only architecture with no runtime dependency on provider credentials.

</details>

<details>

<summary>Improved</summary>

* Centralized management compared to Lite workflow.
* Unified translation pipeline across providers.

</details>

<details>

<summary>Fixed</summary>

* None (initial release).

</details>
{% endupdate %}
{% endupdates %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://julestools.gitbook.io/julestools-docs/changelog/readme-6.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.