There has been a request to split a string into two by adding context to them: http://core.trac.wordpress.org/ticket/22724. The string is “Random,” and is used in both galleries and the links widget. The same string was also used for both in 3.4. I am inclined to leave it as is for 3.5 and deal with it in 3.6. Does this affect you? Please comment to the ticket.
Updates from Andrew Nacin Toggle Comment Threads | Keyboard Shortcuts
Hello all, there were two (very short) strings added after WordPress 3.5′s string freeze to account for some final changes to the media UI:
- “Add to Gallery”, the title of a screen. There is also “Add to gallery” (a button), which was added previously.
- “Reverse order”, used on a button to flip the sort order of a gallery.
Two more strings already existed, but they moved from the admin to the frontend. If these strings were longer, I would try to manually copy it over from the other project, but it is probably easier if you just re-translate it:
- “No items found.”
- “Set featured image”
I appreciate your understanding.
Our target release date remains Wednesday, December 5, 2012. Zé asked for a prediction as to time. I’m not sure yet, but the window would be between 1600 UTC and 2330 UTC, hopefully toward the earlier side but you never know.
Strings for WordPress 3.5 are now frozen.
The targeted release date remains December 5, 2012 (the same date we announced at the start of the cycle).
Unfortunately, this means I’m very late in formally declaring a string freeze. This is entirely on me and I accept responsibility for the delay.
With the exception of the About page, we’ve had only a handful of string changes over the last week. Most translations seem to be in fantastic shape this release, which is a great sight to see. I hope all of you are able to step up and push through.
If you find any typos or other issues, please report them to http://core.trac.wordpress.org/. If you have any questions (or are just plain frustrated with me), feel free to leave a comment.
WordPress 3.4.2 has been released. No string changes from 3.4.1 or 3.4. It does contain some security fixes, so please build and release.
wppolyglots has moved to make.wordpress.org/polyglots!
Note you’ll now be using WordPress.org usernames here. If there are any issues, let me know.
All of your existing subscriptions were transferred over (post or comment subscriptions via email, RSS, or Jabber). We also automatically mapped WP.com usernames to WP.org usernames when transferring the posts.
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.
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.