Strings like 'out of stock', 'cart' and 'My Account' are not transltated to Hebrew in the website although they are translated in the .po file.
Wordpress version - 4.7.2
Woocommerce version - 2.6.13
Avada version - 5.0.5
As you can see in the GitHub repository Theme-Fusion/Localization-l10n which stores Avada translation files contributed by users, the strings 'out of stock' and 'My Account' are not translated to Hebrew.
You can :
download this file,
add your own translations,
compile it to a .mo and
upload it to your wp-content/languages/theme/ folder.
Before attempting to make your own translations, we suggest checking the pre-created language files that ships with Avada. All these files have been contributed by our amazing users and the amount of translated strings might vary.
Better, you can submit your own translations by following the instructions provided by Theme Fusion.
Related
I have a wordpress plugin in english. I have just added .po and .mo files to the /languages folder to support Spanish. However, the localisation is not showing.
I don't believe I have to load the text-domain because I'm using a recent Wordpress version.
Do I need to add something else to make this localisation active?
I have spent hours scouring for a simple answer to this question, to no avail. I've tried three translation plugins also to no avail (WPML, CodeStyling Localization and Loco Translate).
All i want to do is provide my client with a way to define text string changes in WordPress for English. There are NO second languages on the site, I simply want to change one English string for another English string (e.g. change "coupon code" to "discount code"). I would have that there is a standard way to do this, either manually by placing files in wp-content/languages, or by using a plugin that provides an admin interface to edit mo/po files.
CodeStyling Localization is recommended by WooCommerce for editing its text strings - it lists all .mo/.po files and lets you edit the .po then regenerate the .mo. This has no discernible effect on the site, though.
To summarise the situation (i am using latest versions of all mentioned plugins and the WP core):
WordPress is installed with no language definition in wp-config.php (does this mean it defaults to en_US or en_GB - I can't seem to discover that either)? UPDATE: I've stuck to specifying en_GB in wp-config.php now so I can be sure of the language WordPress is running in)
WooCommerce is installed and uses the _e() function for all text strings
CodeStyling localization is installed, and I have successfully edited to en_GB mo/po files and saved and regenerated them
I have confirmed via FTP that the .po file shows the converted text strings once saved
None of the text strings have updated on the frontend
I have tried defining the site language as en_GB in wp-config.php to force the en_GB mo/po files to be loaded for woocommerce, to no avail
All I can guess is that:
The site is ignoring the mo/po files because it thinks there's no "translation" needed because WooCommerce is in English and so is my wordpress install - so it's bypassing the translation files completely
There's a confusion between en_US and en_GB meaning the converted strings aren't loading (maybe the site is en_US but the mo/po i am editing is en_GB, so it's not applying them)
Can anybody shed any light on this?
Thanks
I found the problem: the WPML plugin (which is a translation plugin that supports WooCommerce and multiple currencies) was enabled purely for currency support (not for translations), but had its own default English set to en_US (which overrode my wp-config en_GB settings). This meant none of my changes to en_GB mo/po files for WooCommerce were working. As soon as i corrected WPML's locale for English to en_GB, the changes showed up.
I'm building Arabic only website, I'm using the woocommerce, i added the Arabic mo and po files to the woo commerce plugin, and the translation working good in the wp admin pages, but it's not working in the public pages the English language keeps appearing.
I tried other languages like french it works fine for both admin and public pages.
Is it because the Arabic is RTL language or it's something else, any one know what is the problem???
My site: www.yasmeenart.com
does your file
wp-config.php
have this line ?
define ('WPLANG', 'ar');
also when you upload your .po and .mo files to woocommerce, files should be this name:
woocommerce-ar.mo
woocommerce-ar.po
I am using wpml to translate a wordpress site I am building. I have created a custom theme and am using wp_get_archives() to show the archives in the blog section. When I switch to the french side of the site the dates do not get translated. Does wordpress not automatically have its own translation files on hand?
ok, I figured it out. I had put my custom themes .mo file in both my themes language folder as well as my Wordpress language folder. All I needed to do was replace my .mo in /wp-content/languages with Wordpress' fr_FR.mo. So now both .mo files are being included, and all dates are being translated.
I am building a Wordpress blog system in Spanish and I'd like to have the default theme also translated to "es_ES". I am already running this Wordpress installation in Spanish. What I'd like to know is how to do the same with the default theme (twenty-eleven).
This site allows us to download the po file with the translation: http://translate.wordpress.org/projects/wp/3.2.x/twentyeleven/es/default
But I don't know what to do next...
I'd like to know the process. For I have downloaded the PO and MO files from translate.wordpress.org/projects/wp/3.2.x/twentyeleven/es/… and then uploaded them to domain.com/wp/wp-content/themes/twentyeleven/languages however no change occurred...
Thanks.
This post helped me to understand: http://urbangiraffe.com/articles/translating-wordpress-themes-and-plugins/
The missing information in this tuto is that the languages files must be named just like this: if wordpress is set to "es_CL", the .po and .mo files must be named es_CL.po and es_CL.mo and put in the language folder of the theme.
If the file config.php is correctly set to "es_CL" than the system will use the right language files.