3.4.1 has just been released. No string changes. There is a 3.4.x project in GlotPress for you. The revision is 21156 for either tags/3.4 or branches/3.4. This is a security update, so speed is important. Cheers!

[ Edit: I no longer need an answer to this question. ] All translators — Did anyone have a locale.php file (like ru_RU.php) in 3.3 that they no longer included in 3.4? If so, what is your locale? Those files are going to sit there (and be included) after an upgrade, so we need to remove them manually: http://core.trac.wordpress.org/ticket/20974. Unfortunately it is not easy to ascertain which locales used to have them but no longer do.

WordPress 3.4 will be released within the hour. Start your engines.

WordPress 3.4 has now hit Release Candidate stage. That means strings are frozen and we do not expect any changes.

If you find any typos or other issues, please report them to http://core.trac.wordpress.org/.

Browse Happy!

Hello everyone — WordPress runs a site called Browse Happy, which you’ve probably seen, at http://browsehappy.com/. Here’s a bit about it:

Using an outdated browser makes your computer unsafe. Browse Happy is a way for you to find out what are the latest versions of the major browsers around. You can also learn about alternative browsers that may fit you even better than the one you are currently using.

The theme is fully internationalized and I would like to offer it in as many languages as possible.

Like WordPress.org does when directing you to a locale site, Browse Happy will be able to detect your browser’s preferred language and then offer you the ability to view the site in that other language. We will also do either a subdomain or a path to allow direct-linking to a local site (so de.browsehappy.com or browsehappy.com/de/).

You will then be able to link to the localized version in core. Browse Happy is only 29 strings, so I hope to launch with a few languages next week!

Here is the project on translate.wordpress.org. Let me know if you have any questions. Happy translating!

A release of version 3.3.2 is imminent. There are no string changes. This is a security release, so please release as soon as possible.

An important note. One, you can still build from SVN, there is requirement to use GlotPress at this time. Two, I made numerous changes to many locale’s /dist folders — the folder at i18n.svn.wordpress.org where we pull readme.html, wp-config-sample.php, etc. — in preparation for 3.4. You are going to want to use your 3.3 branch or tag for /dist if that is the case. (I made branches for you if they didn’t exist.)

So: Check to make sure you are using the right /dist.

You can check the changelog to your SVN directory here: http://i18n.trac.wordpress.org/log/pt_BR (change pt_BR to your locale folder). And browse yours here: http://i18n.trac.wordpress.org/browser/pt_BR.

And: TEST YOUR BUILDS.

If there are any issues, post here, and I, Zé, and others will do my best to resolve them.

Cross-posting from the GlotPress development blog: Hello, and a call for comments/feedback.

I added persistent caching to translate.wordpress.org, fixed a bug in GlotPress, and tweaked a few things. The result: GlotPress is now super fast. Even the really slow project pages now load in an instant. See for yourself: http://translate.wordpress.org/projects/wp/dev. Let me know if you see anything funky, such as stuck values (caching issues) etc.

I think we are going to turn off the SVN builder for 3.4.

You will still be able to use your SVN directory, and we will continue to pull files from /dist (like readme.html and wp-config-sample.php). But, in order to create a build, you will need to import any po/mo files you have into the wp/dev projects at translate.wordpress.org.

GlotPress is all about collaboration. So others may help, it is preferred that you periodically import your po/mo files there (if you work with a separate tool), rather than importing them at the end in order to do a release. This also isn’t just about collaboration. At some point, I’d like to make it so you can mark your locale as “ready” for a release. Then we will simply create the build for you when we release WordPress.

Request for feedback from East Asian languages for WordPress 3.4 core modifications.

In #8759, I’m looking for feedback for the editor word counts.

In #16079, I’m looking for feedback for the length of auto-generated excerpts.

If you could test the code and post in the relevant tickets, it would be much appreciated.

Need some RTL feedback here: http://core.trac.wordpress.org/ticket/6425. How should be be handling RTL content in RSS feeds?

I’ve updated the list of 3.4 changes:

• New: Localizing commas, as a tag separator
• New: Fields that should always be LTR
• New: Spellchecker language is now translatable
• Changed: How precisely core detects that a language is RTL (it now uses a translated string)

3.4 update: Localizing quotes and apostrophes that go through wptexturize(). More

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.