WordPress.org

Make WordPress Core

Opened 5 years ago

Closed 9 months ago

#13069 closed defect (bug) (fixed)

Use GlotPress list of locales instead of the one in ms.php

Reported by: nbachiyski Owned by: nbachiyski
Milestone: 4.0 Priority: high
Severity: minor Version: 3.0
Component: I18N Keywords:
Focuses: Cc:

Description

GlotPress keeps track of all languages and locales with some information about them. The list there is also well maintained.

Change History (6)

comment:1 @hakre5 years ago

  • Keywords reporter-feedback added

Is this referring to mu_dropdown_languages() in /wp-admin/includes/ms.php ?

comment:2 @nacin5 years ago

  • Keywords reporter-feedback removed
  • Milestone changed from Awaiting Triage to Future Release

comment:4 @iandunn19 months ago

  • Cc ian.dunn@… added

comment:5 @nacin9 months ago

  • Milestone changed from Future Release to 4.0

comment:6 @ocean909 months ago

  • Resolution set to fixed
  • Status changed from new to closed

In 29630:

Language packs: No WPLANG anymore.

  • The WPLANG constant is no longer needed. Remove define('WPLANG', ); from wp-config-sample.php. Populate WPLANG option based on the WPLANG constant. When get_option('WPLANG') is an empty string it will override WPLANG.
  • Introduce translations_api() which is available to communicate with the translation API. Move translation install related functions to a new file.
  • Replace mu_dropdown_languages() with wp_dropdown_languages(). wp_dropdown_languages() is now populated by the translation API.
  • Remove wp_install_load_language() and allow load_default_textdomain() to switch a core translation.

fixes #13069, #15677, #19760, #28730, #29281.

Note: See TracTickets for help on using tickets.