Skip to content
Avada translation files contributed by users
Branch: master
Clone or download
Latest commit 05d61a5 Nov 12, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
Avada recompile for #137 Nov 12, 2019
fusion-builder regenerate es_ES files for fusion-builder Nov 11, 2019
fusion-core recompile for #137 Nov 12, 2019
fusion-white-label-branding Updating language files Oct 30, 2019
.gitignore Remove package-lock.json from the repo Jan 18, 2018
Gruntfile.js refactor grunt tasks Oct 18, 2019
README.md
api-Avada.json recompile for #137 Nov 12, 2019
api-fusion-builder.json regenerate es_ES files for fusion-builder Nov 11, 2019
api-fusion-core.json recompile for #137 Nov 12, 2019
api-fusion-white-label-branding.json Updating language files Oct 30, 2019
package.json Add task to zip files Aug 26, 2019

README.md

ThemeFusion Translations

In this repository you can find translations for all ThemeFusion products, and contribute translations for your own language.

Who maintains this repository

Our translations are community-driven. Anyone can contribute translations for their own language. This repository hosts both the translation files and our Translations-API, so translation file updates are automatically distributed to all sites.

You can find a list of contributors on this page.

How to Contribute

If you find that some strings are not translated for your language, you can use software like Poedit which is free and cross-platform to translate them, and then submit your updated files so we can include them.
IMPORTANT: Make sure sure you are using the latest files for your locale before you start translating them.

You can find instruction on how to fork the repository and contribute back in this GitHub guide.

If you are not comfortable using GitHub for your translations you can also submit them by sending an email to our support team, and we will submit the updated translations for you > support@theme-fusion.com

There is no need to submit .mo or .zip files, we automatically generate these after your translations are merged. The only thing that should be included in your pull-request is an updated .po file for your locale.

Review Process

Once you submit your translations, our team will check your translations and after they pass our inspection they will get merged. While we can not check the correctness of submitted translations for all locales, we check for abusive language and malintent such as spam links. If a member of our team is a native speaker of the submitted language then we also conduct a second check for the correctness of the submitted translations. We urge you to be patient. The above checks can take from a few hours to a few days depending on the locale and number of translated strings.

You can’t perform that action at this time.