Localization For Translators

Localization Guide for Translators & Contributors

This page is for people who want to help localize ChurchCRM by translating or reviewing terms.

Overview

• How to join the POEditor project and start translating
• Where to find missing terms and how to contribute
• Using AI to help with translation batches
• Best practices for high-quality translations

How to Get Started

• Join the project: POEditor ChurchCRM Project
• Request a new language: If your language is not listed, contact a project admin or open a GitHub issue
• Start translating: Pick your language and begin translating missing terms in POEditor
• Track progress: See the Locale Audit Report for up-to-date translation status

How to Add a New Locale

• If your language is not listed in POEditor, request it from a project admin or open an issue on GitHub
• Once added, you can start translating terms for the new locale in POEditor
• After enough terms are translated, the language can be enabled in the ChurchCRM app

Using AI to Translate Batches

• Missing terms are batched in CRM/locale/missing-terms/ (see the AI workflow)
• Open a batch file (e.g., ja-1.json), paste its contents into an AI chat (like Copilot Chat or ChatGPT) with the prompt: "Translate these terms to [language]. Return only the JSON with translations."
• Review and copy the AI's output back into the file, or use an agent to apply the changes
• For large batches, see Localization-with-AI for more details

Best Practices

• Translate full sentences, avoid abbreviations, and check context
• Use consistent translations for repeated UI terms (e.g., "OK", "Save")
• Work in small batches (50–100 terms) for best AI results
• Review context for ambiguous terms

Need Help?

• See the Locale Audit Report for up-to-date translation status
• Ask questions or request help via GitHub issues or the POEditor project