[wp-trac] [WordPress Trac] #20882: Remove strings related to Akismet from WP localization files

WordPress Trac noreply at wordpress.org
Wed Mar 19 07:32:18 UTC 2014


#20882: Remove strings related to Akismet from WP localization files
----------------------------+------------------
 Reporter:  pavelevap       |       Owner:
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  3.9
Component:  I18N            |     Version:  2.0
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:
----------------------------+------------------
Changes (by nacin):

 * keywords:  dev-feedback =>
 * type:  defect (bug) => task (blessed)
 * milestone:  Awaiting Review => 3.9


Comment:

 Akismet 3.0, which will ship around the same time as WordPress 3.9, has a
 20-25% increase in strings. At 173 strings, it's a full 10 percent of all
 frontend strings, which surprised me. It's time for this to happen.

 Akismet will need to:
  * Add an "akismet" textdomain to all of its strings. There is a handy CLI
 tool in develop.svn for this (it is also accessible via
 http://wordpress.org/plugins/{plugin-name}/admin).
  * Add a "Text Domain: akismet" header to akismet.php.
  * Add a `load_plugin_textdomain( 'akismet' )` call on or after `init`.
 I'd recommend only doing this on `admin_init` and then also on the
 frontend when needed (such as when rendering a widget). I imagine beyond
 widgets (which most sites won't use), Akismet doesn't do anything on the
 frontend.

 They have it easy. :-) I will need to:
  * Update the POT harvesting scripts to exclude wp-content/plugins/akismet
 from WordPress, and to treat it as a standalone plugin.
  * Create a new Akismet project on translate.wordpress.org, and have the
 harvesting scripts populate this project.
  * Transfer all existing translations from WordPress to the new project.
 That will cover perhaps half of the strings in 3.0, depending on how far
 along translators get between now and then. (Point is, translator effort
 is not wasted.)
  * Set up language pack harvesting for Akismet. Basically, any completed
 locale will start serving strings to Akismet 3.0-alpha or later, to
 WordPress 3.7 or greater.
  * Add wp-content/languages/plugins/akismet-$locale.po/mo by default to
 international zips, so an initial install doesn't require a separate
 language pack download (unless out of date). We already do this for
 bundled themes.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/20882#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list