1/26/2024 0 Comments Translate plugin poeditNow, check the plugin’s Details section or Development section and find the option for contributing to plugin translation. To start translating, first register for an account on and visit the plugin page that you want to translate. these changes by using the Loco Translate plugin or Poedit standalone software. It is the easiest and at the same time most useful method that not only helps you use the translated plugin, but also helps others to use it for their benefit. Next translate your labels like in the screenshot and refresh your site. The first and most recommended method of translating a plugin is, translating plugins in manually. You can follow the technical steps below, using poEdit to translate but alternatively you can use a WordPress plugin called. Method 1# Translate WordPress Plugin in : Here is a step by step guide on how you can translate the Stripe Payments Plugin into a language of your choosing: 1. The easiest method is to use a plugin called Loco Translate. Open the POT file that you created before. Save the file as it suggests to you (the language code for example frFR.po, esES.po). So let’s check 3 ways to translate the WordPress plugin. Open POEdit File New Choose the language you need to translate your theme into. It helps you to expand your reach and make connections with a much wider audience. You can also use multiple languages for your website so that both global and native audiences can understand your site. So, when you translate your website into the local language, it creates an appeal to the target audience and becomes their first choice. That means if your website is not understandable to your visitors, it will not grow. And there is a saying, “Can’t Read Won’t Buy”. Though English is an international language, only 25% of internet users are native English speakers. In this article, we will show you the 3 easiest ways to translate any WordPress plugin into your own language without any coding. You can easily translate any WordPress plugin to your language and contribute to plugin translations for your own use or for the benefit of others. But don’t worry! WordPress is very flexible in these matters. Most of the developers develop their plugins in English so you need to translate them on your own. Step 2 Go to ' Catalogue ' ' Settings ' Step 3 Fill in ' Language ' and ' Country ' 1). The problem occurs when you want to build a website in your local language. The vast collections of plugins help you to the feature you want to add to your website. In this case, you seem to be doing something not recommended at all, even if you get it to work.One of the main reasons behind WordPress’s popularity is its extreme flexibility. When you see plugins and themes with ready for translation, it means that they include a POT (Portable Object Template) file. Its typical attributes ar an ISO-639 language code followed by the ISO-3166 country code like: pt_BR, pt_PT, es_ES or es_AR. The program will ask you to select the language you want to generate a new file for. To do so, open Poedit and go to File > New. You can use Poedit to pull all the strings from any plugin or theme you’re working on and use this to generate a POT file. WPLANG is used to set your site main language, which will be taken by the plugins, themes, system backend, and everything that has a translation. Step 1: Create a POT File for Your Plugin or Theme. Just remember not to use underscore for the domain name (it's not your case, anyway). To translate the plugin, you need to click on each available string in its original language, then use the Translation field at the bottom to enter your translation: Notice that you can add notes for other translators using the Add comment button on the right. So I would recommend you to move your files to that directory. In this example, the translation files are in a subdirectory, inside the plugin, which is the best way to pack it. Then, the third one: it is the location of the files. The second one is empty, it's not used because it is deprecated. The first attribute is the text domain you are using (the same you use as a second parameter in the e() or _() function to point at the right translation files). Load_plugin_textdomain('aja圎dit','',plugin_basename( dirname( _FILE_ ). I think that, somehow, when you do not declare a text domain, it uses the default that you have set in the wp-config.php.Īfter trying several hooks on my own plugin, this is the one that worked for me, put this at the very beginning of the file: add_action('init', 'yourplugin_init') These two files should be located in /wp-content/languages/plugins/ directory or better use Loco Translate plugin to relocate the translation files in a safe. If you are using a text domain, and you are encouraged to do so, you need to declare it somewhere in your plugin.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |