-
Posts
-
Hello everyone!
Enfold has become a large and wonderfully great WordPress theme. It is used on thousands of websites and seen by thousands of users and visitors. Therefore, I am a little surprised that there is no good way to contribute translations. :(
WordPress and Enfold are certainly used in many languages. The English translation is good, but many people don’t speak English, or at least not well. For example, I come from Germany and speak German. I understand English, but unfortunately some of my friends and colleagues with whom I work on websites that use Enfold do not speak / understand English that good. Therefore, it would be very helpful if Enfold had a good German translation. I know it has a German translation, but it is missing many translation strings and some are weird, so that average users probably don’t understand it.I have seen that there is this post on the forum: https://kriesi.at/support/topic/please-contribute-and-translate-enfold/ where translations can be shared, but that’s not really a good way, is it? Everyone has to find the translations first, download them, upload them to their website, etc. Wouldn’t it be easier to just provide good translations as standard that ship with the theme…?
I found this GitHub repository: https://github.com/KriesiMedia/enfold-language-files where you can contribute translations. I created pull requests to improve the translations for the German language. However, these are not reviewed or merged. :(To simplify the whole process, I suggest introducing translation tools, like:
– https://crowdin.com/
– https://www.transifex.com/
– https://translations.stellarwp.com/Then users can improve the translations and they can be included directly in the theme in the next version.
Hey,
Thank you for your feedback and for your contribution. We will review and merge it soon.
Everyone has to find the translations first, download them, upload them to their website, etc. Wouldn’t it be easier to just provide good translations as standard that ship with the theme…?
When translations are contributed through our support forum or GitHub, we merge them and make them available in the upcoming version.
Since there are only handful of active translation contributors (Italian, Dutch, French, Croatian), we prefer not to use translation tools and send the language files to the contributors in advance. Most updated translations make to the current version.
Please let us know if you’d like to receive the language files in advance and we’ll send them to you as well.
Best regards,
YigitHi Yigit,
thank you very much for your response!
I would still like to explain why I think using a translation platform like Crowdin could be beneficial for Enfold in the long run, even if there are currently only a few active contributors for translations.
From my experience, the main reason why there are so few contributors is the barrier to entry:
Creating an account in your support forum or learning how to contribute via GitHub is something that most users simply won’t do. Especially if they only want to fix a few strings.Platforms like Crowdin lower this barrier:
– users can log in with Google or easily create an account with email address + password
– no technical knowledge is required (like git)
– contributing a single small fix becomes extremely quick
– many people contribute occasionally without ever becoming regular / active translatorsI work for Aternos and we use Crowdin for all translations (see https://crowdin.com/project/aternos). Although we don’t have many dedicated translators, we receive regular contributions from many users who translate only a few strings. These small improvements add up and have helped us provide our website in 20+ languages.
A major benefit of Crowdin is also the built-in quality control: Translations can be upvoted or reviewed/approved before they are included. This keeps the quality high without adding a lot of manual work.
I believe Enfold could benefit from the same advantages, and it would make it much easier for the community to help you maintain high-quality translations.
I would still kindly ask you to reconsider using a translation platform, because I think it could significantly improve both the quality and the amount of translation contributions in the future.
Best,
PaulHi Paul,
I noted it internally for further consideration.
For now, could you please include all changes in the same Pull Request on GitHub? Otherwise, it creates conflicts that we resolve manually.
Thanks again for your contribution and feedback!
Regards,
YigitThen I sincerely hope that translation errors like those in “The Hungarian Phrasebook” don’t creep in.
https://youtu.be/grA5XmBRC6g?si=Mqnuk1FpjPJAipeQ&t=50Please leave technical terms untouched, as they are commonly used.
A button is simply a button, and you can hover it, etc. …If you absolutely want such translations, get the corresponding Lang file from the Lang folder (only po is needed to edit).
Open the po-file in f.e. poedit (free po editor) Search for your Phrase – f.e. “Show Fullscreen Button (HTML5 videos)”
Enter your translation and save (poedit will save the new po-file and generates the concerning mo-file too).
Upload these files to your child-theme/lang/ folder and put this to your child-theme functions.php:function overwrite_language_file_child_theme() { $lang = get_stylesheet_directory().'/lang'; return $lang; } add_filter('ava_theme_textdomain_path', 'overwrite_language_file_child_theme');keep the sequence of variables inside your translation.
F.e. :But we are proud to say that %s contributed %s entries already.
first the name of the author for %s – then the number of contributions for %se.g. for german translations:
Wir sind jedoch erfreut, dass %s bereits %s Beiträge beigesteuert hat.
and not:
Wir sind jedoch erfreut, dass bereits %s Beiträge von %s beigesteuert wurden.
- You must be logged in to reply to this topic.