In 3.4, you no longer need any PHP to customize the defaults for start of week, feed language, or default timezone. (You would have hooked into populate_options for these.)

start_of_week and timezone_string/gmt_offset are now translatable, and rss_language is gone (it uses the site’s locale, now).

I’ve created a page here that outlines all changes to 3.4 so far, including the details for how to set these defaults: Important Changes for WordPress 3.4. I will update it as more changes happen.

For 3.4, the default links are now translatable, both titles and URLs. http://core.trac.wordpress.org/changeset/19781

I left out the URLs for extend/plugins/, themes/, and ideas/ from being translated as there are not yet official localized resources for these, and I would not want to send them off-site. Since the forums are a better conduit for feedback anyway, I demoted Suggest Ideas down the list, moving the Support Forums up one.

Howdy, finally I’ve found time and few volunteers to finish Georgian versions of WordPress. Big part of 3.0 is already translated, what is the best way to merge/import those strings to into 3.3 and dev?

In GlotPress, you may need to export 3.3.x/ms strings and import them into dev.

For 3.4, we’re changing how we split strings into multiple pot files. Since 3.0, we’ve done a generic POT and then a second POT for multisite. We are now going to be doing a frontend POT, an admin POT, and a network admin POT. The projects have been added to GlotPress here and here.

While merging and splitting projects in GlotPress, some strings got orphaned. Before you go re-translate all of the missing strings, first go to translate.wordpress.org/projects/wp/3.3.x/ms, export a po file, and import it into both wp/dev/admin and wp/dev/admin/network. Everything should be back to normal.

Cheers, and sorry for the trouble. For more, see ticket 19852.

In 3.4, you will no longer need to specify a $wp_default_secret_key, in $locale.php or in default-constants.php. For many of you, this means your $locale.php file will now be empty. Branch off 3.3 and remove $locale.php from /trunk/dist/ if that is the case. See ticket 19599 for more.

Hi,I’m already translate Jetpack’s 1.2.1 versions Turkish language package. Who could approve my translations?

Hi,I’m already translate Jetpack’s 1.2.1 versions Turkish language package. Who could approve my translations? I’m translated about 10 pages word and I’m go on.

For 3.4, WP is going to use frontend, admin, and network admin pot files rather than the current wordpress and ms pot files. For background, see ticket 19852. We’re currently shuffling around the “Development (future 3.4)” project to accommodate this new pot split.

All locales: In 3.4, you will no longer need to override wp-admin/setup-config.php. The strings in this file will now be included in the POT, and the config file will be generated properly regardless of the wp-config-sample.php placeholders such as “your_username_here”. See [19760] and #18180.

tl;dr – POT imports are fixed.

You can read more of the problem and the solution in the commit message. Many thanks to @pdoes for the patch.

A fun fact – marking all unchanged strings as removed led to the fun situation where almost all strings were removed, than on the next update (in 1 hour), then on the next they are brought back and so on

Continents and Cities were added to GlotPress, but when I tried to build package, related .po and .mo files were not added to package. Everything else is OK. Any idea?

RTL locales: In 3.4, you will no longer need to specify $text_direction = 'rtl'; in your $locale.php file. Please remove it from $locale.php, and if this makes your $locale.php empty, then remove the file. (Please branch /trunk/ off into /3.3/ first, in case there is a 3.3.2.)

The following locales have been included: ar, ckb, fa_IR, he_IL, ug_CN, dv, fa_AF, ha, ps, uz_UZ, yi. If you are missing (or are incorrectly included), let me know.

Does anybody know if the original POT files are automatically imported every hour around the 59 minute mark? This could be an indicator of the missing strings people see.

Hello people, I would like to help translating articles from english to spanish, I’m a native spanish speaker with advanced english and I’ve found several untranslated articles, my concern is that most of them were the documentation ones, wich I think are very important ones to be avaliable in several languages since they are the way WordPress can actually be useful for spanish only speakers.

Hello My name is Zakariye, I would like to add Somali to the list of languages and I would also like to help volunteer to translate in Somali. Thank you for your concern