Howdy polyglots,
BuddyPress 1.7 is now in Release Candidate 1 (read our announcement) and we are now in string freeze for the translations. 
Tagged: string freeze Toggle Comment Threads | Keyboard Shortcuts
-
Paul Gibbs
-
Andrew Nacin
We’re still aiming to release WordPress 3.5 tomorrow (target is 16:00 UTC). In the meantime, we’ve made two more string changes in the interest of clarifying some of the gallery settings. Both suggestions came from translators (and others) —
- “Random” (with the context “gallery order”) is now “Random Order”
- “Describe this image…” is now “Caption this image…”
Note there are also “Describe this audio/video/file…” strings, but they can only be triggers by plugins for WordPress 3.5, so I didn’t want to needlessly give you three more strings to translate.
That’s it, by the way. We’ve continued to make a few tweaks but at this point, if it hasn’t been proposed or reported, we’re done.
You guys rock, talk to you tomorrow!
-
Ze Fontainhas
Thanks for the update. Could we have a .pot harvest run as soon as possible, just to make sure everything’s in place?
-
Andrew Nacin
Yep, I made sure it ran before I posted this. There are still some translation-set caching issues with GlotPress, but I’ve refreshed that (and added it to my list for things to look into).
-
Milan Dinić
I’ve looked into that and proposed a patch here.
-
-
-
Andrew Nacin
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.
-
Ze Fontainhas
…hopefully toward the earlier side but you never know.
I guess #wordpress-dev on freenode (IRC) is your friend
-
Andrew Nacin
String Freeze
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.
-
Kazama
Thanks for the heads up, Nacin.
-
Birgit Olzem
Thank you! German is completed.
-
Dominik Schilling (ocean90)
I like.
-
-
-
DjZoNe
Thank you! Hungarian is 100%.
However I hope, string freeze will happen earlier next time -
Ze Fontainhas
Portuguese is at 100%
The targeted release date remains December 5, 2012
Any prediction as to when (UTC) during that day?
-
Andrew Nacin
If I had to declare a window, it would be no earlier than 4pm UTC and no later than 10pm UTC.
-
-
martian36
Some strings added after Nacin’s String Freeze comment.
Korean is 100%.
Andrew Nacin
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/.
Andrew Nacin
A few string changes:
- http://core.trac.wordpress.org/changeset/19571 — “Contributing Developers”, a string that the credits API will be returning. (Reported here on wppolyglots.)
- http://core.trac.wordpress.org/changeset/19569 — We accidentally left in a few references to “Admin Bar” when it should now be “Toolbar”.
Both of these changes came from reports from translators. This is all we’ve had since string freeze, and all we are likely to have, unless one of you notice something else.
As a reminder, we’re moving very swiftly to a final release. It may happen Monday. I will post here as we are running through the release checklist (as in, 15–60 minutes before release). It should be noted that we never release if there was a change to core in the previous 24 hours, so I will try to post here with some additional lead time as well.
-
Zé
I just want to know about my beer
-
Remkus de Vries
Beer? What happened to Dry Martini’s?
-
Zé
Dry Martini threshold is at 10 new strings
-
Remkus de Vries
Roger that!
-
-
-
-
Rasheed Bydousi
Thanks
-
Gabriel Reguly
How about building the packages from GlotPress?
Will it be possible for 3.3? Unfortunately it was not for 3.2.1
Regards,
Gabriel-
Zé
Was just testing that for gd and it’s working.
-
-
Gabriel Reguly
Sorry Zé, but I can’t build it.
I get “Invalid source .” for either subversion or GlotPress.
-
Zé
I’ll check. It’s pt_BR?
-
Remkus de Vries
It’s working fine for me with nl_NL. I just built a 3.3-RC2 without a hitch..
-
Zé
@gabriel, could you place the correct .po’s in svn? I only see continents-ctites and core, and I’d need also ms and the themes .po’s there. in particular, you seem to be missing the twentyten and twentyeleven folders. Example: http://i18n.svn.wordpress.org/pt_PT/trunk/messages/
-
Gabriel Reguly
Surely, I have them at tags/3.3 (Same as I have done for 3.2.1)
Will place them at trunk then, just one moment please.
-
Gabriel Reguly
Ok, all is there now, but I still can’t make a build.
http://i18n.svn.wordpress.org/pt_BR/trunk/messages/
BTW, I see pt_PT has licenca.txt and license.txt. Do I need to add those files too?
And one minor thing, probably for @nbachiyski, when exporting from GlotPress one gets pt-br file names, ideally they would be named pt_BR instead. Does it make sense?
Thanks fo all help until now.
-
Zé
Works fine for me… (on br.wordpress.org)
BTW, I see pt_PT has licenca.txt and license.txt. Do I need to add those files too?
If you want to, it’s not mandatory.
-
Gabriel Reguly
Ok, I can make a build now, as I have changed computers.
Seems the error is at the build page: if I change source from Subversion to translate.wordpress.org it disables the dropdown for Project:, hence causing the build error.
Does anybody else has this issue? (I am using Firefox)
-
Zé
That’s just a cute JS bug with the dropdown. If you change the upper one to the blank entry and then back to ‘trunk’ for instance, the lower one should behave properly again.
-
Gabriel Reguly
Ok, thanks for all the help.
Now I am ready for 3.3
-
-
Andrew Nacin
Can we remove all dist/license.txt files? The english version from the core package/svn should take precedence.
Additionally, any translated license files must include (a translation of) the WRITTEN OFFER available at the end of license.txt.
-
Zé
Ok to remove. I don’t think the translated version is linked from anywhere, to begin with.
-
-
-
-
Andrew Nacin
We’re in string freeze.
Heads up on timing: We’re aiming to release 3.3 final before December 13.
Please post here and use the “core” tag if there are any issues, typos, etc. If we need to change a string, I will post here (and beg for forgiveness). Tickets with potential string changes will be marked with the ‘i18n-change’ keyword.
-
Mattias Tengblad
Before is when?
-
Andrew Nacin
We haven’t discussed the timing yet, but RC is going well. We will be in RC for at least a week and translators will have at least one weekend. At the time of this writing, 41 languages are at greater than 90%, so it seems things are in very good shape.
-
Mattias Tengblad
Sounds good. Please remember to notify us something like 12 to 24 hours before release
-
-
-
Akerbeltz
What’s the deadline for translations? I have all done bar core which is at ~60% – keeps fluctuating cause someone keeps dumping new strings in it
I note that quite a lot of locales are in the same broad area… what’s the deal here if you don’t have 100% on the cutoff day? Sorry for the noob questions, not been through a l10n release on wordpress before.-
Zé
You don’t need to release at the exact same time, especially not if it’s the first time WordPress is translated into a particular language. Just translate at you normal pace and release when you’re ready. (and by the way, “string freeze” = “no one dumps new strings”. If there are new strings, @nacin buys everyone drinks)
-
Andrew Nacin
I buy @vanillalounge drinks. He covers yours.
-
-
Andrew Nacin
First “string” change is likely to be this: http://core.trac.wordpress.org/attachment/ticket/19427/19427.diff. I would beg forgiveness, but I’ll save that for string changes that will actually affect your amount of work.
-
Zé
I’ll have a beer
Kenan Dervišević
Andrew Nacin
WordPress 3.2 has now hit RC1. That means we’re in string freeze.
If there’s something we absolutely need to change, we will, but I’ll be updating you here. Potential string changes will be monitored on Trac using the i18n-change keyword.
Please note, the freeze does *not* apply to Twenty Eleven. We’re not quite done there yet.
-
Remkus de Vries
For those of you who want to build a RC1 for download, use Revision 18306.
-
Stas Sușcov
In the credits page, the group titles are not translatable:
diff --git wp-admin/credits.php wp-admin/credits.php
index ea0d62c..df54daa 100644
--- wp-admin/credits.php
+++ wp-admin/credits.php
@@ -106,7 +106,7 @@ foreach ( $credits['groups'] as $group_slug => $group_data ) {
} elseif ( isset( $group_data['placeholders'] ) ) {
$title = vsprintf( translate( $group_data['name'] ), $group_data['placeholders'] );
} else {- $title = $group_data['name'];
+ $title = __( $group_data['name'] );
}echo '' . $title . "n";
-
Milan Dinić
This is fixed in [18315].
But there are two titles that are not: XML-RPC Developer and Twenty Eleven.
-
Andrew Nacin
You’re right, but both have a reason:
- The string is now “XML-RPC”, as of [18242]. I just haven’t changed the API response yet.
- At one point, I queried GlotPress and seem to recall that Twenty Ten was almost never translated. I’m not positive, but I think that’s why I never added the Twenty Eleven string — assumption that it will not be used.
Shall I add it?
-
Zé
I vote against. “Twenty Eleven” is the theme’s name in any language, and shouldn’t be translated, the same way “WordPress” shouldn’t.
-
Stas Sușcov
+1
-
Milan Dinić
I do transcribe WordPress to Cyrillic form Вордпрес, this is practice that happens in Serbian for core software names.
-
-
Milan Dinić
I don’t personally translate themes names but this string is available for translation elsewhere so someone might translate it.
-
Milan Dinić
There is a change in readme.html You can see difference here: http://core.trac.wordpress.org/changeset?reponame=&new=17302%40trunk/readme.html&old=16896%40trunk/readme.html
-
Xavier
Thanks Milan.
Sergey Biryukov
A new string was added to wordpress-ms.pot recently: http://i18n.trac.wordpress.org/changeset/15556. So far it’s the only change since the string freeze.
Andrew Nacin
With WordPress 3.1 Release Candidate 1, strings are now frozen. If there happen to be any string changes required (which we will carefully consider for necessity), I will post here. We have nothing in the queue and I wouldn’t expect much if anything.
If you find a string that is incorrect or contains a typo, let us know.
-
Milan Dinić
When can we expect a release?
Note that you should warn us about exact timing at least 24 hours before, we discussed about that issue around 3.0 release.
-
Andrew Nacin
We don’t know yet. When we’re ready, we’ll release.
-
Andrew Nacin
We’re going to be freezing strings for WordPress 3.1 today soon. You can begin your final push for 3.1.
If we have any string change after the final freeze (which I’ll announce here), we will also post it here. (We don’t make those changes lightly, so they need to be particularly critical.)
We have a few more things to change today, so I’ll announce the freeze when we’re done.
-
Remkus de Vries
Thanks for letting us know.
-
Milan Dinić
To take this opportunity to ask where are post format slugs used, I’m not sure should we translate them?
-
Sergey Biryukov
See _post_format_request() and _post_format_link() in wp-includes/post.php. I’ve decided not to translate them as I typically don’t use Cyrillic slugs and prefer them to be used only for posts.
-
Andrew Nacin
In a twist, the slugs are actually translatable into the blog’s language. So “type/gallery” can be “galleria” or whatever works.
-
Milan Dinić
So they are used only in post formats archives, right?
-
Sergey Biryukov
Yep, it seems so.
-
-
-
Peter Westwood
Updated Post: To
todaysoon as that is what nacin meant
Final Freeze will be announced when it happens
fernandot 6:54 pm on March 28, 2013 Permalink |
Nice job