I18N component

Recent posts on the make/core blog

View all posts tagged i18n.

93 open tickets in the I18N component

93 open tickets defect (bug) enhancement feature request task (blessed)
5.2 4 0 0 1
Awaiting Review 24 35 5 0
Future Release 7 10 0 1
WordPress.org 1 0 0 1
5.3 0 4 0 0

93 open tickets. Last 7 days: -1 ticket

8 tickets that have no replies

View list on Trac

  • #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
  • #39756  Extend the jQuery datepicker localization ui
  • #42271  i18n: Merge two similar translation strings in option pages
  • #43802  Default timezone for new sites in WP multisite administration multisite
  • #46336  Support custom WP_PLUGIN_URL in load_script_textdomain()
  • #46387  Undefined index notice in wp-includes/l10n.php on line 950
  • #46446  Language files are not deleted when the twenty-* themes are deleted

9 tickets slated for 5.3

View list in Trac

  • #41305  Add lazily evaluated translations rest-api performance
  • #42223  Merge two similar translation strings when using get_space_allowed() multisite
  • #44360  Missing translators comment need to be added coding-standards
  • #44541  Text length should be localizable
  • #44662  Text length of the Incremental search of link in tinymce should be localizable
  • #44721  The privacy data erase fulfillment email should be in the user's language privacy
  • #44865  class-wp-locale.php has a condition always false rtl
  • #45371  Add tag: Use `event.isComposing` to support input method editor (IME) converters accessibility
  • #46056  The personal data export email for privacy requests should be in the users locale administration privacy

93 open tickets

Open bugs: 36. 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: