Localization

🌍 Translation Guide

Thank you for helping make TagForge accessible to creators worldwide!

This guide outlines the simplest way to add a new language or improve an existing translation. No coding knowledge or GitHub experience is required.

---

🚀 Quick Start

1. Find your file: Look in Assets/Localization/ for an existing language or use en-US.json as a template.
2. Translate: Edit the text on the right side. Keep the keys on the left and special symbols ({0}, \n) exactly as they are.
3. Submit: Upload your file to a Translation Issue. I will handle the code integration!

---

📂 Step 1: Get the File

You only need a simple text editor (Notepad, VS Code, etc.) to work on these files.

1. Navigate to: Assets/Localization/ in this repository.
2. Download: Use en-US.json as your template for new languages, or open an existing language file if you want to improve it.
3. Rename (New Languages): Use the format language-COUNTRY.json (e.g., de-DE.json or pt-BR.json).

---

✍️ Step 2: Translation Rules

Open your file in any text editor.

[!WARNING]
Do not change the keys on the left side. The app uses these keys to find the text. If you change them, your translation will not load.

{
  "Settings.Title": "Settings",      // ❌ DON'T CHANGE LEFT
  "Settings.Save": "Enregistrer"     // ✅ TRANSLATE RIGHT
}

⚠️ Critical Rules

Feature	Rule	Example
Placeholders	Keep {0}, {1} intact. You may move them to fit your grammar.	"Loaded {0} models" → "{0} modèles chargés"
Newlines	Keep \n intact. This forces a line break in the UI.	"Error.\nTry again" → "Erreur.\nRéessayez"
Quotes	Keep \" intact. This displays a literal quote mark.	"Say \"Hello\"" → "Dites \"Bonjour\""

[!IMPORTANT]
Syntax Watch: Ensure every line (except the last one) ends with a comma ,. Do not remove the curly braces { } at the start and end of the file.

---

📮 Step 3: Submit Your Translation

I handle all the code and technical integration. You just need to provide the file!

1. Go to: New Translation Issue.
2. Attach: Drag and drop your completed .json file into the issue description.
3. Submit: That's it! I will review the file, register it in the app, and include it in the next update.

---

[!NOTE]
UI space is limited. Prefer short, punchy translations over literal ones (e.g., "Save" vs "Click here to save").

[!NOTE]
If you are unsure about a specific term or context, feel free to ask in Discussions or mention it in your Issue.

Happy Translating! 🌍