[wp-trac] [WordPress Trac] #20974: Remove obsolete locale-specific files on upgrade

WordPress Trac wp-trac at lists.automattic.com
Tue Jun 26 07:58:08 UTC 2012


#20974: Remove obsolete locale-specific files on upgrade
----------------------------+------------------
 Reporter:  SergeyBiryukov  |       Owner:
     Type:  defect (bug)    |      Status:  new
 Priority:  low             |   Milestone:  3.5
Component:  I18N            |     Version:  3.4
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |
----------------------------+------------------
Changes (by nacin):

 * keywords:   => has-patch
 * milestone:  3.4.1 => 3.5


Comment:

 Though I posted to [http://wppolyglots.wordpress.com/2012/06/26/all-
 translators-did-anyone-have-a-locale/ the P2], I was able to sufficiently
 script this.

 These locales had a locale.php file in their latest 3.3.x build but not in
 their 3.4 final build: sv_SE
 pl_PL
 ar
 id_ID
 nb_NO
 fi
 en_CA
 nn_NO
 eo
 ckb
 pt_BR.

 zh_CN, he_IL, and ru_RU still do have locale.php files.

 All of these locales are either $wp_default_secret_key or $text_direction,
 so they are harmless. pl_PL also adds a date declension filter, but again,
 harmless as-is and won't break core. So, moving to 3.5.

 This is not as easy as just adding files to `$_old_files`, because we have
 to detect a custom language directory. Here's a patch that is one way to
 implment this.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/20974#comment:5>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list