[wp-trac] [WordPress Trac] #17268: Use native gettext library when available
WordPress Trac
noreply at wordpress.org
Tue Sep 5 09:32:38 UTC 2023
#17268: Use native gettext library when available
-------------------------------------------------+-------------------------
Reporter: linushoppe | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone: Future
| Release
Component: I18N | Version:
Severity: normal | Resolution:
Keywords: has-patch needs-refresh needs-unit- | Focuses:
tests dev-feedback | performance
-------------------------------------------------+-------------------------
Comment (by swissspidy):
The core performance team recently conducted an
[https://make.wordpress.org/core/2023/07/24/i18n-performance-analysis/ in-
depth i18n performance analysis], which confirmed the performance penalty
localized WordPress sites pay today. The blog post presented and compared
multiple solutions to this problem—including the native gettext extension,
but also different approaches like using raw PHP files for translations.
The latter turned out to be the most promising approach and now we want to
test it at a wider scale using a dedicated plugin, appropriately named
[https://wordpress.org/plugins/performant-translations/ Performant
Translations].
I would love for you all to first read the performance analysis and then
check out the feature plugin on your site(s).
[https://wordpress.org/plugins/performant-translations/ Download the
plugin]
* [https://make.wordpress.org/core/2023/09/05/call-for-testing-performant-
translations/ Call for Testing post]
* [https://github.com/swissspidy/performant-translations Contribute on
GitHub]
--
Ticket URL: <https://core.trac.wordpress.org/ticket/17268#comment:111>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list