colinleroy

This plugin has no setting or UI. It just does one thing : use the php-gettext library to handle translations. This results in much faster translation than using the default PHP gettext implementation of WordPress.
If the extension is not available, the plugin will simply do nothing.
You can verify that the plugin is working by looking for an HTTP header: X-Native-Gettext: 1, that will be sent as soon as a string will be translated by the native library.
If your WordPress install is in English, this plugin has no purpose. Otherwise, it can help speed up your install quite a lot.
Requirements: 
– php-gettext 
– OS-level support for the locale(s) you want to translate to.

Native Gettext for WordPress

Great Plugin.

It does one job and it does very good!

With the help of the Query Monitor Plugin, I was able to measure a drop of almost 45% of PHP memory usage using "Native Gettext for WordPress" for a simple Dashboard-request.
Really cool.

The plugin author is answering friendly and helpful to support requests.

Fast & Friendly

No problems found, after testing on several sites. My sites are all heavily dependent on fast loading of text domains, and all have the PHP gettext extension. PHP 8.0 and 8.1.

However, may not work in combination with other WordPress plugins overriding load_textdomain.


Works as it says, fast

A very light wrapper plugin that uses the native gettext library for faster localization.

Alex Kirk

This plugin ensures that any text coming from a translation file (<code>.po</code> or <code>.mo</code>) is run through an escaping function before it is output to the user.
Escaping refers to the modification of the text so that special control characters do not have an effect (for example <code><</code> in HTML).
Example: If an original text does not contain HTML, then a translated text should not be allowed to contain HTML either. Thus, an HTML link introduced by a translator should have no effect because this was not intended by the developer.
This plugin is in the proof-of-concept stage, it was created to test if the escaping of translated text can be handled in a general way, whether it severely affects the performance of a site, and if it breaks things.
For text without HTML, the text is sent through <code>esc_html()</code>, for text containing HTML tags, it is sent through <code>wp_kses()</code> which is provided with a list of allowed HTML tags and attributes, derived from the original string.
Thus this plugin tries to show a generic way of how to make sure that translated text is escaped. This is something that can eventually be ported to core.

Secure Gettext

Escapes translated text before it gets output. This adds an extra security layer around translated text.

Native Gettext for WordPress vs Secure Gettext