On the dashboard, the language shown is the one in your profile, front-end is the one in general I would first argue that maybe you could help get your language correctly translated on if there’s something incorrect there 🙂 We didn’t announce this due to that We don’t need load_plugin_textdomain, we did test this out and translations do work fine without it. This was a conscious decision because that folder hasn’t been updated in years, and all the language files were copied over to the repo anyway so they are either the same if untranslated or more up to date.Īdditionally, those files managed by WordPress are given priority in the core languages folder anyway, so in theory, you’ll be using those anyway by default. We have deprecated the langs folder as more up-to-date translations are on the repo. I downloaded the formal German translation from above link and I have got exactly what I do not want to get and why I maintain each language file by myself because of lacking professionality, see this example of this translation
PORTUGUESE BRAZILIAN AS POEDIT FILE SUGGEST CODE
Some work is probably required to make the PHP code localization-ready No load_plugin_textdomain call and lacking metadata In D:\\WordPress\Plugins\Events Manager\events-manager_v5.9.7\events-manager\events-manager.php: header "Text Domain" = "events-manager" In D:\WordPress\Plugins\Events Manager\events-manager_v5.9.7\events-manager\events-manager.php: header "Plugin Name" = "Events Manager"ĭ:\WordPress\Plugins\Events Manager\events-manager_v5.9.7\events-manager\events-manager.php is the main plugin file
Unfortunately Poedit cannot generate the pot file from the plugin, see the error message of Poedit below: Analyzing WP directory D:\WordPress\Plugins\Events Manager\events-manager_v5.9.7\events-manager I’m working with Poedit for years and I know about this tool.
0 kommentar(er)
