Remove the requirement to call load_plugin_textdomain() or load_theme_textdomain()
|Reported by:||johnbillion||Owned by:||swissspidy|
|Component:||I18N||Keywords:||has-patch has-unit-tests commit|
In the near future we'll start to see some plugins and themes which do not bundle any translations, instead relying on all translations being powered by language packs from translate.wordpress.org. In this situation, the load_[plugin|theme]_textdomain() call falls back to the WP_LANG_DIR/[plugins|themes] directory.
It makes sense then that the requirement for such a plugin or theme to call load_[plugin|theme]_textdomain() could be removed, because the translation now lives in one of two known locations, and as long as MO files were loaded JIT.
The first time core encounters a localised string with a textdomain that has not already been loaded, it should look for a corresponding MO file first in the WP_LANG_DIR/plugins directory and then in the WP_LANG_DIR/themes directory, and load it if it's found.
Change History (46)
15 months ago
- Keywords has-patch has-unit-tests added; needs-patch removed
- Milestone changed from Awaiting Review to Future Release
- Resolution fixed deleted
- Status changed from closed to reopened