Hi, Can you post the URL to your site please.
Perhaps the Finnish language file name doesn’t match the active language e.g. fi_FI
https://www.elaintenviikko.fi/
Filenames are
speakout-fi_FI.mo
speakout-fi_FI.po
No, it has not.
I’ve tried copying the language files to WP’s language folder (where a language file for Akismet was, for some reason), installing various multilingual plugins, switching the site language back and forth from fi_FI to en_Us and back.
I also tried installing it to other Finnish language WP sites and a Swedish language site and the translations did not work in any of them.
So do you happen to know any easy way of manually translating the strings without having them overwritten whenever the plugin updates?
Translation happens normally at https://translate.wordpress.org/projects/wp-plugins/speakout/ But there is no Finnish translation there.
the platform will automatically generate a language pack when the “stable” project reaches at least 95% translated and approved strings. (But right now, there even is no stable project, probably the plugin needs to push a new version to the repo for this.)
Since WordPress 4.6 the preferred place for Finnish translation of this plugin would be /wp-content/languages/plugins/speakout-fi.mo
(Note that Finnish is one of a few languages where WordPress does not use the country part in the locale. Ref: https://make.wordpress.org/polyglots/teams/ )
Hmmm, that’s interesting @tobifjellner about the country part of the file name. Hadn’t see that before.
@slramela try renaming wp-content/plugins/speakout/languages/speakout-fi_FI.mo to speakout-fi.mo and let me know if that works. If it does I can rename it in the plugin.
Sadly, renaming the file did not help.
I also tried copying the translation file to /wp-content/languages/plugins/ and that did not help either, regardless of whether I edited the load_plugin_textdomain function call to point to that folder or not.
But that is just me taking shots in the dark.
BTW, @tobifjellner I looked at the translate.wordpress project and most of the strings there seem to be from readme.txt file, is that normal?
A typical plugin will have four translation projects for each locale.
– Stable
– Stable readme
– Development
– Development readme
Where “Stable” contains the strings for the version of the plugin that is currently being served to users from the plugin directory. (This sub-project is currently missing for this plugin, probably because of some configuration issue in the plugin itself, often due to incorrect text-domain)
“Stable readme” are strings from the plugin readme that will be used in the localized version of the plugin directory. (Like fi.wordpress.org/plugins/ )
“Development” and “Development readme” are strings from the /trunk subdirectory of the plugin directory. Since translations are automatically propagated between Development and Stable, the Development sub projects can be used to prepare translations before a new version of the plugin is pushed to stable.
I just checked the i18n-readiness for this plugin a bit more in detail.
This plugin has set “Stable tag = trunk”. This means that “Development” is the version actually being used.
@123host Your readme.txt is 28k, please reduce its size to not more than 10k. Usually this is easily achieved by moving old changelog lines to a separate changelog.txt file.
You’ve got both readme.md and readme.txt, so only the .txt one is used.
I managed to fix the problem for myself and force the right language file to be loaded by putting this into my functions.php file:
$text_domain = 'speakout';
$override_language_file = ABSPATH . 'wp-content' . DIRECTORY_SEPARATOR . 'plugins' . DIRECTORY_SEPARATOR . 'speakout' . DIRECTORY_SEPARATOR . 'languages' . DIRECTORY_SEPARATOR . 'speakout-fi.mo';
// Unload the translation for the text domain of the plugin
unload_textdomain($text_domain);
// Load the override file
load_textdomain($text_domain, $override_language_file );
If that works, excellent! But why not make the over-write load the included file speakout-fi_FI.mo? That way you will get updates to the language when they happen.
@tobifjellner thanks for the info. I have reduced readme.txt to 10kb as suggested.
Another topic, maybe since you are involved with WP you can help. SpeakOut! was forked from a plugins speakup that has been abandoned. It hasn’t been updated in 6 years yet it is still available in the plugin repository and being downloaded. Is it possible to get a dead plugin removed?
@123host email plugins@wordpress.org with details about the abandoned plugin
