-
-
Notifications
You must be signed in to change notification settings - Fork 0
Localization
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.
-
Find your file: Look in
Assets/Localization/for an existing language or useen-US.jsonas a template. -
Translate: Edit the text on the right side. Keep the keys on the left and special symbols (
{0},\n) exactly as they are. - Submit: Upload your file to a Translation Issue. I will handle the code integration!
You only need a simple text editor (Notepad, VS Code, etc.) to work on these files.
-
Navigate to:
Assets/Localization/in this repository. -
Download: Use
en-US.jsonas your template for new languages, or open an existing language file if you want to improve it. -
Rename (New Languages): Use the format
language-COUNTRY.json(e.g.,de-DE.jsonorpt-BR.json).
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
}| 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.
I handle all the code and technical integration. You just need to provide the file!
- Go to: New Translation Issue.
-
Attach: Drag and drop your completed
.jsonfile into the issue description. - 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! 🌍