I18N component

Recent posts on the make/core blog

View all posts tagged i18n.

84 open tickets in the I18N component

84 open tickets defect (bug) enhancement feature request task (blessed)
4.9.7 1 0 0 0
5.0 3 5 0 0
Awaiting Review 17 21 3 0
Future Release 11 19 2 1
WordPress.org 1 0 0 0

84 open tickets. Last 7 days: +1 ticket

12 tickets that have no replies

View list on Trac

  • #38675  Add user language chooser to wp-signup.php
  • #39295  Prevent infinite loop when calling get_user_locale() in a 'locale' filter
  • #39673  wp_dropdown_languages() shows wrong list of installed languages, when 'languages' is empty
  • #39675  Remove unnecessary admin notification about deprecated `WPLANG` administration
  • #39756  Extend the jQuery datepicker localization ui
  • #42271  i18n: Merge two similar translation strings in option pages
  • #42355  Missing plural forms in "unexpected output" string
  • #42721  Introduce native language name as a WP_Locale property
  • #43096  Reduce redundant calls to translate() performance
  • #43424  Use access modifiers in POMO library
  • #43802  Default timezone for new sites in WP multisite administration multisite
  • #43864  A comment inside an i18n function will cause makepot/extract.php to miss the string

8 tickets slated for 5.0

View list in Trac

  • #17268  Use native gettext library when available performance
  • #20491  Introduce some JavaScript i18n functions javascript rest-api
  • #41305  Add lazily evaluated translations rest-api performance
  • #42223  Merge two similar translation strings when using get_space_allowed() multisite
  • #42721  Introduce native language name as a WP_Locale property
  • #42818  i18n Tools have PHP 7.2 compatibility issues
  • #43304  Data type of deprecated parameter of load_plugin_textdomain function should be bool and not string docs administration coding-standards
  • #43829  [proposal] Add unit test for Japanese language

84 open tickets

Open bugs: 33. View list on Trac

Help maintain this component

Component maintainers:

Many contributors help maintain one or more components. These maintainers are vital to keeping WordPress development running as smoothly as possible. They triage new tickets, look after existing ones, spearhead or mentor tasks, pitch new ideas, curate roadmaps, and provide feedback to other contributors. Longtime maintainers with a deep understanding of particular areas of core are always seeking to mentor others to impart their knowledge.

Want to help? Start following this component! Adjust your notifications here. Feel free to dig into any ticket.

Contributors following this component: