Toml (#5115)

# Description of Changes

<!--
Please provide a summary of the changes, including:

- What was changed
- Why the change was made
- Any challenges encountered

Closes #(issue_number)
-->

---

## Checklist

### General

- [ ] I have read the [Contribution
Guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md)
- [ ] I have read the [Stirling-PDF Developer
Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/DeveloperGuide.md)
(if applicable)
- [ ] I have read the [How to add new languages to
Stirling-PDF](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md)
(if applicable)
- [ ] I have performed a self-review of my own code
- [ ] My changes generate no new warnings

### Documentation

- [ ] I have updated relevant docs on [Stirling-PDF's doc
repo](https://github.com/Stirling-Tools/Stirling-Tools.github.io/blob/main/docs/)
(if functionality has heavily changed)
- [ ] I have read the section [Add New Translation
Tags](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md#add-new-translation-tags)
(for new translation tags only)

### Translations (if applicable)

- [ ] I ran
[`scripts/counter_translation.py`](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/docs/counter_translation.md)

### UI Changes (if applicable)

- [ ] Screenshots or videos demonstrating the UI changes are attached
(e.g., as comments or direct attachments in the PR)

### Testing (if applicable)

- [ ] I have tested my changes locally. Refer to the [Testing
Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/DeveloperGuide.md#6-testing)
for more details.

scripts/translations/README.md

@@ -2,6 +2,12 @@
 
 This directory contains Python scripts for managing frontend translations in Stirling PDF. These tools help analyze, merge, validate, and manage translations against the en-GB golden truth file.
 
+## Current Format: TOML
+
+**Stirling PDF uses TOML format for translations** in `frontend/public/locales/{lang}/translation.toml`.
+
+**All scripts now support TOML format!**
+
 ## Quick Start - Automated Translation (RECOMMENDED)
 
 The **fastest and easiest way** to translate a language is using the automated pipeline:
@@ -451,18 +457,15 @@ python scripts/translations/translation_merger.py fr-FR apply-translations --tra
 
 ## Translation File Structure
 
-Translation files are located in `frontend/public/locales/{language}/translation.json` with nested JSON structure:
+Translation files are located in `frontend/public/locales/{language}/translation.toml` with TOML structure:
 
-```json
-{
-  "addPageNumbers": {
-    "title": "Add Page Numbers",
-    "selectText": {
-      "1": "Select PDF file:",
-      "2": "Margin Size"
-    }
-  }
-}
+```toml
+[addPageNumbers]
+title = "Add Page Numbers"
+
+[addPageNumbers.selectText]
+"1" = "Select PDF file:"
+"2" = "Margin Size"
 ```
 
 Keys use dot notation internally (e.g., `addPageNumbers.selectText.1`).
@@ -478,7 +481,7 @@ All scripts preserve placeholders like `{n}`, `{total}`, `{filename}` in transla
 ### Automatic Backups
 Scripts create timestamped backups before modifying files:
 ```
-translation.backup.20241201_143022.json
+translation.backup.20241201_143022.toml
 ```
 
 ### Context-Aware Translation