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!
Tagged: release Toggle Comment Threads | Keyboard Shortcuts
-
Andrew Nacin
-
Andrew Nacin
WordPress 3.4 will be released within the hour. Start your engines.
-
Mattias Tengblad
Thanks for heads up 🙂
-
SteveAgl
Great!!!
-
Remkus de Vries
Bring it on!
-
Sergey Biryukov
ru_RU is done 🙂
-
Andrew Nacin
It’s out! http://wordpress.org/news/2012/06/green/
-
Mattias Tengblad
-
Xavier
Oh, right: fr_FR is out too! Trois-point-quatre pour tous ! 🙂
-
coachbirgit
de_DE is done, too! 🙂
Many thanks to all, who helped out and worked on it!
-
Gabriel Reguly
pt_BR is ready.
However is was done using trunk and HEAD.
Please enable 3.4 and 3.4.x
-
Gabriel Reguly
Update: we are having a WordCamp this weekend, will postpone until monday.
-
Andrew Nacin
Huh? What are you postponing? Just release it.
I will work on enabling 3.4/3.4.x but trunk and HEAD will be fine for the moment.
-
Gabriel Reguly
Yep, I know trunk and HEAD are fine for now.
Later it will be used 21078, correct?
Anyway it is the revision of the translations that is not complete yet. 😉
Cátia and Diana will be doing a final effort to make the release during the WordCamp or the next monday
-
Andrew Nacin
You can use translate.wordpress.org; tags/3.4 or branches/3.4 for dist files (if you have those), “Development (trunk)” for GlotPress. Revision 21078 is proper, yes.
I will create a 3.4.x GlotPress project but I first want to implement project branching in GlotPress so you don’t all need to re-import your translations.
-
-
Gabriel Reguly
pt_BR is released. 🙂
-
-
-
Mark Thomas Gazel
I’m getting the same error in SVN (da_DK) as the last time. Can’t access the tags-folder.
I managed to create af branch 3.4 folder with a dist-folder inside. So I could build from that, but @nacin would you please look into it? I would like the tags-folder ind place too.
-
Andrew Nacin
I’m not getting any errors. In the future, please screenshot or copy the exact error as well as the settings you used. I just created a 3.4 build from da.wordpress.org using translate.wordpress.org; tags/3.4 for dist files, Development (trunk) for GlotPress. Worked like a charm.
-
Mark Thomas Gazel
Thank you. I’ll remember screenshots.
Your build was missing the danish dist-files.
I think it was because the files were in the root-folder, tags/3.4 and not tags/3.4/dist/
But I had access to SVN and made some adjustments, so everything is fine and released now.
Thanks again
-
-
-
Bage
Tamil(Sri Lanka) has been released.
-
frilyd
Norwegian nynorsk released, too 🙂
-
jiehanzheng
Any ideas why Twenty Ten and Twenty Eleven are not updating when using the automatic update? Users are reporting that after they update the themes separately, the lose the translation files for their themes…
-
Gabriel Reguly
Same issue here, pt_BR files for Twenty Ten and Twenty Eleven are included in the package built.
But when updating the themes, the translation is lost.
Looks like is its a known problem https://wppolyglots.wordpress.com/2011/07/13/twenty-eleven-losses-translation-after-3-2-1-update/#comment-3597
-
-
drssay
ko_KR is done!!
-
Dan - Lucian Ștefancu
ro_RO up this morning
-
-
Rasheed Bydousi
Can anyone tell approximately when WordPress 3.4 will be released officially?
-
Mattias Tengblad
It’s at least a week left since thats the time frame for the string freeze.
-
Andrew Nacin
We’re no longer operating on a strict two-week window. GlotPress has allowed the efforts of one release rather seamlessly roll over into the next release, and it enables us to easily see what kind of progress is being made. I would expect WordPress 3.4 to drop as early as this week.
-
Jenia Laszlo
Jetpack 1.3 will be released in a couple of days, and the Automattic team would love it if you could help out with translations, especially Spanish, Portuguese, French, German, Italian, and Dutch (all regional flavors welcome 🙂 ).
The GlotPress project has already been preloaded with translations pulled from WordPress.com and previous Jetpack versions. There are 465 strings in this release, and many languages are already above 50%.
There is a slight chance that a couple of strings will change before the release, as 1.3 is still going through the final testing. We’ll post a note here if that happens.
If you would like to have a language added to Jetpack and/or or want to be assigned as a validator for your language (especially if you already validate WordPress translations), please leave a comment and we will help you out.
Thanks in advance for your help!
-
Gabriel Reguly
Hi Jenia,
Did some more translations for pt_BR, but GlotPress is not behaving well with this translation:
↵ Sent by a verified %s user.
It issues this error message, event if I just do ‘Copy from original’
Warning: Original and translation should both begin on newline.
Regards,
Gabriel-
Zé
Reproduced. Even if you insert a newline in the translation, it gets stripped. Hence it’s both a GP issue (stripping the newline) and a Jetpack issue (why does a string need to start with a newline character, to begin with?)
-
Remkus de Vries
There are quite some strings in WP with the same newline character.
-
Jenia
Thanks to y’all for the reports, we will be looking into this.
-
-
Andrew Nacin
If someone can put this into a GlotPress ticket, I can look.
-
-
mdawaffe
I removed the leading newline from the source and copied the translation of the previous string to the new one.
-
Gabriel Reguly
Thanks for fixing it.
-
-
-
SteveAgl
Can add the wordpress validators as me for jetpack too? thanks
-
Jenia
Ciao, I added you as the validator for Jetpack 1.3 in Italian. Thanks for your help!
-
-
Wacław J.
Is it possible to set per-project validators?
-
Jenia
You bet. There can be different validators per project or per sub-project (e.g. someone can be a validator for WordPress.com but not Jetpack, or be a validator for Jetpack 1.2 but not 1.3). Why? 🙂
-
Wacław J.
How do I do that?
-
Jenia
You need to be able to grant validator permissions, i.e. be a GlotPress admin for that install. In case of Jetpack in particular, someone from Automattic (me, for example) can assign different validators per project. If you need help with that, just let me know (although I am not sure why you would need that, since only the active translation project of Jetpack is important).
-
Wacław J.
Great to know that. Thanks. 🙂
-
-
-
-
-
Carlos Eduardo G. Barbosa
Can you include, please, Sanskrit (sa_IN) with me as validator?
I am working on Sanskrit for WordPress 3.4, and it would be nice to have Jetpack plugin translated also.
Thank you.-
Jenia
Here is the project: http://translate.wordpress.com/projects/jetpack/1.3/sa-in/default
What is your wordpress.com username, please?
A good start is to import .po of whatever translations you already have available (wordpress.org, in your case) – saves some time.-
Carlos Eduardo G. Barbosa
My WP.com username is carledug.
Thank you.-
Jenia
You’ve been added as a validator for Jetpack in Sanskrit (sa-in), thank you for your help!
-
-
-
-
Carlos Eduardo G. Barbosa
The string ‘Resore this item from the Trash’ is mispelled. Please correct it.
-
Jenia
I am not finding this string (might have been fixed between when you saw it and now), could you please post a link here if you are still able to see it? Thank you!
-
Carlos Eduardo G. Barbosa
The mispelling is still found at
http://translate.wordpress.com/projects/jetpack/1.3/sa-in/default?filters%5Bstatus%5D=either&filters%5Boriginal_id%5D=43539
-
-
-
Martin (IQ)
What are freedom levels? Could you explain what is meant with that in order to find a good translation. 🙂
-
mdawaffe
The publisher of a VideoPress video may flag the video to never use flash: the video may only be played in an HTML5 video capable browser.
If your browser does not support HTML5 video, that “freedom levels” message is shown.
The link is to http://www.gnu.org/philosophy/free-sw.html
-
mdawaffe
I agree it’s not a very helpful error message 🙂
-
Martin (IQ)
I agree. 🙂 And it’s a translators nightmare as well. I’ve checked several translations (with the help of translate.google.com) and found not one that made sense to me. Indeed, I would go so far as to say that a lot of them are translated completely wrong and in a misleading way.
What this error message basically wants to say is “Your browser doesn’t support HTML5 video playback”, right? So why not just saying this? I know it’s tempting to mention some gnu philosophy here and there but why do you give us translators such a hard time?
-
mdawaffe
Technically it’s “The author of this video has decided it may only be played using non-proprietary technology. Your browser must support HTML5 video playback (an open technology) to play this video”.
The intention was not to give translators a hard time. The intention was to promote open technologies. It’s just badly written.
The string isn’t going to change for this release of Jetpack.
-
Martin (IQ)
Thanks for clarification. This helps at least to find a better translation. 🙂
-
Martin (IQ)
btw. the translations of “freedom levels” I’ve found range from “plains of freedom” to a very free translation of “you’re not authorized”.
-
-
-
-
-
-
KardiWeb
Hello Jenia,
I would like validators to request access to the hungarian translation.
Thank you -
KardiWeb
Username: idesignsmedia and no kardiweb. please repair.
-
mdawaffe
Jetpack 1.3 is about to launch. Thanks so much for all your time and efforts. We really appreciate it.
We’re happy to launch 1.3.x releases to improve translation, so please don’t let this 1.3 release stop you from contributing if there’s more to do in one of your languages 🙂
-
Wacław J.
Can you set me as a validator for Polish?
-
Jenia
Sure, username waclawjacek added as a validator for Jetpack – Polish.
-
Wacław J.
Thanks. 🙂
-
-
Andrew Nacin
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.
-
Gabriel Reguly
Thanks for the heads up.
-
Rasheed Bydousi
Done.
Thanks. -
Gabriel Reguly
pt_BR is released.
As a side note, we use tags for the builds.
Yet, I had a look at branch 3.3 and seemed to me tha it was originally 3.1.1 ?!?! Is that correct? Should not it had come from 3.3.1?
-
Bage
ta_LK has been released.
We also used tags to build it.
-
Mark Thomas Gazel
I might need some help here. Or som e pointer.
Using the repo-browser in Tortoise I can’t access the dist-folder for 3.3.1. Get this error:
PROPFIND of ‘/!svn/vcc/default’: could not connect to server
(http://i18n.svn.wordpress.org)So should I take the dist-folder from either branch og tag 3.3 and put in an 3.3.2-folder. And then reuse the messages-folder from 3.3.1 and put it in the 3.3.2-folder also?
-
Gabriel Reguly
Today I have found that pt_BR was broken for themes.
For the build, I have selected the usual (for me) option:
translate.wordpress.org (dist/ files will still be taken from Subversion)
But because the GlotPress files were empty, the build got no translations. Yet they where present at Subversion.
I had the same issue for 3.2.1, instead that time it was the opposite: the strings where not present at Subversion, but at GlotPress. So that time I built from SVN.
I wonder which would be the recommended option for building 3.4, will it use GlotPress as suggested?
Regards,
Gabriel
Andrew Nacin
The release of 3.3.1 is imminent. It is a security and maintenance release. There are no new strings. Please deploy promptly. Thanks!
-
Gabriel Reguly
Thanks for the heads up.
-
Gabriel Reguly
pt_BR is build, tested and released. 🙂
Andrew Nacin
3.3 is about to be released.
-
Zé
Gentlemen, start your engines.
-
Rasheed Bydousi
Engines ready!
-
-
Remkus de Vries
Changeset 19591?
-
Zé
Grabbing HEAD should give you a 3.3
-
Zé
That came out wrong… 😛
-
Remkus de Vries
Prefer getting 🙂
-
Zé
Moving on
-
-
Remkus de Vries
But really, how do I grab HEAD?
-
Zé
You should build from core 3.3, GP dev, and HEAD should be pre-filled (PS I can’t see a 3.3 tag for nl in svn)
-
Remkus de Vries
It’s not pre-filled and I can’t remember it ever has been. I have always had to enter the specific changeset number to get the proper build.
I have added both a 3.3 tag and a 3.3 branch for nl and I can select both in Rosetta .. so I should be good 🙂
-
Zé
Try writing ‘HEAD’ in the version field
-
Remkus de Vries
That worked. Just built it and released it 🙂
-
-
-
-
-
-
-
Mattias Tengblad
3.3 sv_SE is done 🙂
-
Gabriel Reguly
3.3 pt_BR is done 🙂
https://twitter.com/#!/greguly/status/146573214393446400
Andrew Nacin
Expect a final release of WordPress 3.3 in the next 10-36 hours.
-
Gabriel Reguly
Thanks for the heads up.
-
Rasheed Bydousi
Thanks for the update.
Peter Holme Obrestad
WordPress 3.3-Beta2 released, svn revision 19023 (hope I am correct about this 🙂 )
frilyd
As mentioned many times before, validators often unintentionally release beta versions (aortic dissection etc). I’m far from the only one with this problem: Many of us are simply translators with too little time. What I’d like, is something very simple, like “release the latest stable WordPress in nn_NO from Glotpress”. It would be a great relief not to have to worry about file revision numbers ever again. Please, can it be?
-
Andrew Nacin
I’ll take a look.
Andrew Nacin
3.2.1 imminent. No string changes.
-
Remkus
Changeset 18439 I presume http://core.trac.wordpress.org/changeset/18439
-
Andrew Nacin
Yep. As always, build off the tag to reduce screw-ups.
-
Remkus
Hmm, but when I use that one I get
$wp_version = '3.3-aortic-dissection';
in version.php
-
Andrew Nacin
You need to build off tags/3.2.1 or branches/3.2, not trunk.
-
Remkus
Am I the only one having this issue? I’ve tried to build it from various changesets but I keep getting 3.3-aortic-dissection in version.php. Is this perhaps related to GlotPress still serving 3.2 from Trunk?
-
Kenan
Remkus, make a build from SVN. There is no branch for 3.2 in GlotPress, just Development (which is now 3.3). bs_BA is released also :).
-
Gabriel Reguly
Nancin or Zé or someone else must apply the same fix that was used for 3.1.1 https://wppolyglots.wordpress.com/2011/04/11/otto42-gave-me-a-heads-up-that-some/
-
Gabriel Reguly
Remkus posted this one at the 3.1 release time: https://wppolyglots.wordpress.com/2011/02/27/hi-there-if-you-want-to-build-a/
And Nikolay solved the issue: https://wppolyglots.wordpress.com/2011/02/27/hi-there-if-you-want-to-build-a/#comment-1501
-
Remkus de Vries
@vanillalounge and @nbachiyski have you seen this?
-
-
-
Gabriel Reguly
Please make Project: 3.2 available.
(Project name at translate.wordpress.org. Determines which version of WordPress you will get.)Currently we only have trunk, 3.1 & 3.0 options.
Trunk was fine for 3.2, but it is not for 3.2.1 😦
-
Rasheed Bydousi
I am building ar-AR from tags 3.2.1 but i get 3.3-aortic-dissection in version.php.
What’s changed ?
-
-
-
Rasheed Bydousi
There should be a 3.2 version at:
wp-admin/tools.php?page=rosetta_manage_translationsMeanwhile i have deleted wp-ar 3.2.1 because it shows 3.3-aortic-dissection in the admin dashboard.
Please provide a solution.
Thanks.
-
Rafael Poveda - RaveN
You can try this:
Use subversion
Create tags/3.2.1 in SVN and use it as locale
Use tags/3.2.1 as WordPress
Use revision number 18439You will have 3.2.1 version ready to publish
-
Rasheed Bydousi
Thanks Rafael.
-
Gabriel Reguly
Sorry Rafael, that does not work for building from translate.wordpress.org, which is the way I use to build pt_BR packages.
Could you elaborate on the subversion solution?
I am guessing that I should get the .mo files from glotpress, but I don’t know where to place them at the svn.
Thanks in advance.
-
Sergey Biryukov
Placing them like this should be enough to build from SVN:
tags/3.2.1/messages/pt_BR.mo
tags/3.2.1/messages/ms-pt_BR.mo
tags/3.2.1/messages/continents-cities-pt_BR.mo
tags/3.2.1/messages/twentyeleven/pt_BR.mo
tags/3.2.1/messages/twentyten/pt_BR.mo-
Peter Holme
I had to add the .po-files as well… then it worked. nb_NO is out 🙂
-
Remkus de Vries
Where can I find the continents-cities pomo?
-
Zé
The .pot is here: http://i18n.svn.wordpress.org/pot/trunk/wordpress-continents-cities.pot
-
Remkus de Vries
Never knew that one existed. If I use GlotPress that is all taken care of then?
-
-
-
-
Gabriel Reguly
Thanks Sergey, fortunately Nikolay fixed the issue and I could use the glotpress translations.
However I will keep your instructions in hand for 3.3 🙂
-
-
-
-
-
-
-
jiehanzheng
China all set.
-
Rafael Poveda - RaveN
es_ES ready.
-
kuzman0v
mk_MK ready but it shows 3.3-aortic-dissection in the dashboard. I build it from SVN.
-
Nikolay Bachiyski
The 3.2 projects are now in GlotPress: http://translate.wordpress.org/projects/wp/3.2.x
You can import your translations there and then use the
3.2 and 3.2.x
project to build 3.2.1 from GlotPress.-
kuzman0v
There are no string available and nothing happens when I import the .po file.
-
Rafael Poveda - RaveN
3.2 have no strings at all
-
Zé
Update is forthcoming
-
-
kuzman0v
Working perfect now. Thanks.
-
-
Gabriel Reguly
Thanks Nikolay, pt_BR is finally released now.
Peter Holme Obrestad
It seems the dist file `/wp-admin/setup-donfig.php` has been revisioned since 3.1… So, heads up (a little late) 🙂
-
Zé
-
Peter Holme
ah, thanks 🙂
-
Stas Sușcov
Zé, somebody double posted your thread again 😀
-
Zé
POIDNH
-
-
Sergey Biryukov
WordPress 3.1.4 is released. According to the changelog, there are no string changes.
-
Gabriel Reguly
Thanks Sergey,
pt-BR is ready, revision log number is 18378 – from http://core.trac.wordpress.org/browser/tags/3.1.4
-
anotherkaz
I can’t create the new package of 3.1.4 for Thai at th.wordpress.org
everytime I tried, I got the white page. Any advice?
suscov
You can use rev. 18043 to compile the builds.
-
Stas Sușcov
-
Andrew Nacin
Ideally you should build off the tag, never branches, and only trunk when doing a build for a beta or RC candidate.
-
Stas Sușcov
Hmm, I don’t see any difference.
-
-
Gabriel Reguly
Thanks for clarifying it Nancin.
Just to make it double checked, you are talking about the following, right?
http://core.trac.wordpress.org/browser/tags
So for 3.1.3, it is 18044, correct?
Milan Dinić
WordPress 3.1.3 is released. Changelog tells that there are no string changes nor changes at dist files (except version in readme.html, of course).
-
Rafael Poveda - RaveN
Already in es_ES (we have been the fastest this time! :D)
-
Milan Dinić
Well, sr_RS was up before this post, so… 😉
-
-
Gabriel Reguly
Thanks for the announcement Milan.
For those using glotPress, release number is 18044.
And pt_BR is ready too.
-
Andrew Nacin
Sorry for not posting the release here — it’s a part of our checklist, unfortunately we had some issues discovered immediately after release, so we got distracted. Once I got here, this post was already up. Cheers!
Gabriel Reguly 1:46 am on June 28th, 2012 Permalink |
Thank you Nacin, pt_BR is ready.
Bage 4:44 am on June 28th, 2012 Permalink |
ta_LK is ready. Thank you.
Rafael Poveda - RaveN 6:23 am on June 28th, 2012 Permalink |
es_ES ready.
Emre Erkan 7:52 am on June 28th, 2012 Permalink |
tr_TR is ready
Rasheed Bydousi 7:58 am on June 28th, 2012 Permalink |
How long we should wait until the update appears in Dashboard? I’ve been waiting for half an hour to see the Arabic version but it still does not appear in Dashboard. In the past the new update appeared within 5 minutes. What changed this time?
Andrew Nacin 1:03 pm on June 28th, 2012 Permalink |
WordPress caches update checks for 12 hours. You’d have to visit Dashboard > Updates to cause it to check now. The Arabic API response looks good here: http://api.wordpress.org/core/version-check/1.6/?debug&locale=ar
Dan - Lucian Ștefancu 8:52 am on June 28th, 2012 Permalink |
ro_RO ready
Milan Dinić 9:19 pm on June 29th, 2012 Permalink |
You made error in URL of 3.4.x project Trac source, /browser is missing.
Zé 9:25 pm on June 29th, 2012 Permalink |
Fixed, thanks.