French translations of all WPManageNinja plugins
Hello everyone,
I'm in the process to translate ALL WPManageNinja plugins to French (some are partially translated, other have 0 translations). First I'll contribute to the official WP plugin repository translation platform, and this is valid for the free versions of plugins (hosted on wordpress.org), and probably ask to become the "PTE" for those plugins.
Then I'm thinking of a repository where I would submit the translations for the Pro versions. (Unless WPMN has a repository to commit to? Shahjahan Jewel ? )
I'll also document my process because these are several thousands of text strings and generic AI translations are not doing the work.
However, a long-time French contributor to the WP Polyglots team created a Claude skill that take all the official rules of the French polyglot team, grammar, typography, glossary for consistency, etc. and this creates far better results (still to be manually checked, which is what I'm doing right now).
With everything documented, other language translators could benefit, and in the long term, all the plugins would get to 100% translated much faster.
Please comment :)
Merci. ce serait génial. J'utilise LOCO translate avec API OPENAI. Seulement il y a quelques chaines de caractères récalcitrantes. Je viens d'ailleurs de déposer un post à ce sujet. Je pense que toutes les chaines ne sont pas disponibles. Merci en tout cas. Je fais aussi quelques chaines à la main car ca bugge quelques fois
DAVID MOUSSEBOIS I'll update here when done
One "collaborator" has translated Fluent Plugins to Spanish with AI, and that work IS A REAL DISASTER. And the worst part, the revisers are approving that bad work. Every time I can, I go to change/correct those bad translated strings, but it's an unending task... 😢
Jose Luis Duron I know :)
If just telling an AI "translate this to XX language" it won't work, but this Claude skill I'm mentioning is using the real official glossary and rules from the official French team (WP Polyglots).
That's why I want to document everything so other language translators can replicate the process.
And there are so many text strings in WPMN plugins :D
This surfaced an issue (Shahjahan Jewel, where can I report? EDIT: I opened a support ticket)
FluentCommunity did not take into account the language selected by the user, but only the main site language (as defined under Settings-General), so users could select a language in their WP profile and language files be present, it would only stay in the main site language (which is wrong). I want different languages to be served to my users (international community). So I asked Claude for a snippet (add as snippet or mu-plugin), and here is it:
add_filter( 'locale', function ( $locale ) {
if ( is_admin() || ! is_user_logged_in() ) {
return $locale;
}
$user_locale = get_user_meta( get_current_user_id(), 'locale', true );
return $user_locale ?: $locale;
} );
and now it works, and the community is shown in the user language.
Claude commented:
It's intentionally scoped to the frontend only so it doesn't mess with the admin. The effect is that get_locale() behaves like get_user_locale() for logged-in users — fixing FluentCommunity and, as a bonus, any other plugin with the same bug.
When you report it, the key detail to give them is that they should replace get_locale() with determine_locale() in whatever PHP bootstraps the React app — that's the WP-native function that already handles user locale, site locale, and admin locale correctly depending on context. Makes it an easy fix on their end.