Skip to content

Localization

Charles edited this page Jul 14, 2017 · 11 revisions

Supported Languages

ChurchCRM Supports Localization is 20+ languages.

Want to help translate this project?

Join the Project on POEditor

Supported languages

Fully translated

  • French
  • Portuguese
  • Spanish

Need Help

  • Albanian
  • Arabic
  • Central Khmer
  • Chinese (simplified)
  • Chinese (traditional)
  • Dutch
  • English (AU)
  • English (CA)
  • German
  • Hungarian
  • Italian
  • Norwegian
  • Polish
  • Romanian
  • Russian
  • Spanish
  • Swedish
  • Thai
  • Vietnamese

Localization Providers

For PHP server-side code, ChurchCRM uses gettext: GNU gettext Manual For JavaScript client-side code, ChurchCRM uses i18next: https://www.i18next.com/

Generate Master Localization file

  • ssh into vagrant box
  • cd /vagrant
  • Run npm run locale-gen
  • Review changes in /vagrant/src/locale/messages.po
  • Commit messages.po
  • Create a Pull Request for changes
  • Upload to POEditor.com
  • Tag the terms with the release version

Update Localization

  • got to poeditor.com
  • update locale values for terms
  • download po and mo file to your locale server for testing

Download Localization

  • Go to POEditor.com and genrate an API Key
  • Add the API Key to Build BuildConfig.json
  • ssh into vagrant box
  • cd /vagrant
  • Run npm run locale-download
  • Review Changes
  • Commit Changes
  • Create a Pull Request for changes
Clone this wiki locally