id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc
18960,Localised installs no longer receiving translations for bundled themes,dd32,dd32,"As part of [17576] (#14484) updating of bundled themes was removed from the core update process. The bundled theme updates process was left to the standard theme updater.

As a result of this, Translated builds no longer receive updated translation files (as the .org version of the theme does not contain any translation files).

This was a known issue for 3.2, however, Language packs were to take over for 3.3, and that hasn't happened.

Note: Previous to the above changes, If a user updated their bundled theme after updating core, they'd lose translation files too.

We need to include some way for localised builds to receive bundled theme translations, either:
1. Actually include translation files with the theme (which is what every other theme would be doing) - Language Packs will remove the need for that
2. Include twentyeleven/twentyten language files in wp-content/languages/ - but I don't believe the load_textdomain() call will load from there? 
3. Forcibly copy wp-content/themes/twenty(ten|eleven)/languages/ over during the update process when wp-content/themes/twenty(ten|eleven) exists - This will still result in translation loss when a user updates their theme after core.

3 is a band aid until language packs eventuate, and seemingly the best option if 2 isn't possible. 1 has downsides over all copies ending up with a tonne of extra language files which may or may not be used.

See: http://wppolyglots.wordpress.com/2011/10/15/hello-translation-for-twenty-eleven-isnt-included-in/ and http://wppolyglots.wordpress.com/2011/07/13/twenty-eleven-losses-translation-after-3-2-1-update/",defect (bug),closed,normal,3.5,Upgrade/Install,3.2,blocker,fixed,has-patch commit,knut@… aesqe@…