We’ve been hammered with spam on the Dutch forum lately and that has resulted in a not so flattering tag cloud http://i.remk.us//ej/vzrof9qfscgkc.png
Recounting via the bbPress tool results in a internal server (500) error. Please advise sir @nacin
We’ve been hammered with spam on the Dutch forum lately and that has resulted in a not so flattering tag cloud http://i.remk.us//ej/vzrof9qfscgkc.png
Recounting via the bbPress tool results in a internal server (500) error. Please advise sir @nacin
Hey @vanillalounge ,
Can you please deploy Rosetta Forum to the Dutch forums please? I know it’s not finished yet, but we’re working on that.
Thanks!
Thanks! It is tagged with Request though.
This is where GlotPress keeps weirding me out: http://cl.ly/0520243U2f0Q021B2006 Every single view shows there a no strings left to translate, but yet it keeps nagging me about 5 untranslated strings. Is this a cache issue or a bug @nacin?
We are finishing up the Dutch translation for Jetpack – finally – but we have one request. Currently an empty jetpack-nl.po is added to the download where this should be jetpack-nl_NL.po
Is there something I can do to have this changed properly or …
Sent a note to @beau.
on twitter?
on Skype
don’t have you on skype yet Beau
Run, Beau!
Hmm … So that’s going to be fun in January ..
Just added you Beau..
I noticed today that upgrading TwentyTen and TwentyEleven to their 1.3 version make said themes loose their translations if they previously had some. Any idea who to talk to about this and / or where. Perhaps you know @nacin ?
Yeah, it’s a flaw I’ve experienced too. Also with earlier upgrades of the default themes.
Yeah, we hosed you on this one. In 3.4 this will absolutely be handled.
Is it an option to add the current available locales to a 1.3.1 version?
Is there a way, other than asking here, to update the po/mo on the nl.wordpress.org site to the latest 3.3 version? I want to make a new screenshot but it looks rather silly with New in the toolbar instead of Nieuw
The screenshot is updated on the site itself, mijnheer. Goto to Appearance → Header and upload the appropriately dimensioned image. As to the translation of rosetta itself, make sure it’s complete on GlotPress and then request a deploy from Tools → Deploy Requests
Screenshot I knew, but I had not completed the Rosetta translation. Just finished that and requested a deploy.
Saw it, deployed. Give it 5 minutes to propagate.
It’s been 20 minutes and it doesn’t seem to be updated. Wait longer or… ?
Example?
http://cl.ly/CZ3I and http://cl.ly/CZCH for example..
Problem with the rosetta.pot. Looking.
Still?
keep calm & carry on
alrighty then
Oy,
How can we have the translations updated on our xx.wordpress.org sites? I’d love to see the fruits of my labor in fy.wordpress.org and nl.wordpress.org. As long as we don’t have any language packs just yet, the only thing I can do is bug you @vanillalounge ?
By ‘translations’ I assume you mean a fresh rosetta.pot? If so, I’m on it.
I actually meant the actual translation in Dutch and Frisian I see when I am logged into those websites.
Right, rosetta.pot, as per http://codex.wordpress.org/International_WordPress_Sites
I somehow always think of the extra stuff – like the deploy stuff – on the international sites as the rosetta.pot. Not the actual translations we create in GlotPress .. but hey, if that’s what you mean, go for it
rosetta.pot is a superset of WordPress, i.e. it’s WordPress (duh) with a few additional features, like deploy requests and the packaging and releasing of downloadable versions.
Gotcha, thanks Zé!
When I look at the current NL Credits page I see myself and four other people as with Gravatar above ‘rest of the translators’. I assume that’s because somehow those usernames have validators or something, but none of them are (anymore). So please @vanillalounge please remove usernames edde, grizzler, mklijmij and basszje from the validator list and add afoka and rubenw to that list.
I’m the only one that is on that list and supposed to be. Could also because of something @nacin did not panning out perfectly though. Either way, the four mentioned above should be removed regardless.
Everyone you mention are validators in the system. Validators should be 100% accurate with the system, as they’re easy to query. The other translators, not as much — that query might need work.
Odd.. because rubenw and afoka or not being displayed as validators and to my knowledge edde, grizzler and basszje have never been. mklijmij has been one three years ago (pre GlotPress that is ).
user basszje can approve strings with locale nl and slug default
user afoka can approve strings with locale nl and slug default
user rubenw can approve strings with locale nl and slug default
user DeFries can approve strings with locale nl and slug default
user edde can approve strings with locale nl and slug default
user mklijmij can approve strings with locale nl and slug default
user grizzler can approve strings with locale nl and slug default
well.. all I can say is that the four mentioned before should be removed, and afoka and rubenw are not currently being shown on the credits page.
Screenshot: http://cl.ly/7RzN
edde, grizzler, mklijmij and basszje can no longer validate, but afoka and rubenw were there all along.
OK – bug confirmed on my end. Validators used to be stored a completely different way, I was pulling from that list. Need some time to switch it over.
Glad you found the cause. And thanks BTW for the addition of the validators. Greatly appreciated by a lot of Validators I can asure you.
One related but off topic about the profile link provided. The profile currently does not show any activity on the international forums. Is that something that can be fixed?
+1
Thanks Zé.
Would you please add: defries, afoka and rubenwoudsma ( or rubenw, I’m not sure ) to the bbPress GlotPress project.
nl?
nl_NL, yes.
Done (and it’s ‘rubenw’)
Best. Drumming. Ever.
Thanks!
I’m guessing that with the release of the bbPress 2.0 beta plugin the translation will soon be added to translate.wordpress.org?
+1
http://translate.wordpress.org/projects/bbpress/plugin/
** Please use a separate thread to request new locales/validators ***
Thanks Zé. Will do.
We talked earlier about updating the xx.wordpress.org sites to a more current WordPress version and a new theme. We were told that we needed to wait ’till 3.1 dropped and this is me checking in again
Anynews on this?
I’ll add it to my list and I’ll discuss it with Zé. Hopefully soon.
Great, thanks!
When I build a the new 3.1.1 version now and choose the following in Rosetta:
Locale branch: Tags/ 3.1.1
Project 3.1 and 3.1.x
WordPress Revision: HEAD
WordPress version: 3.1.1
I end up with a 3.1.2-alpha version which obviously is not what I should be getting. Is there a way to select to get the 3.1.1 tag from SVN?
I used WP revision number 17609 and it is OK. But Emre said 17595 to use. So change your revision to 17609 or 17595.
That did the trick. Was not aware we could choose the version in that manner. I had tried to enter revision numbers there before but I always got an error. Works now, so thanks!
You can always check tags for revision numbers: http://core.trac.wordpress.org/browser/tags
It’s the safest way to make things right for now.
3.1.1 was tagged in 17595 – so this is the version number to use.
http://core.trac.wordpress.org/changeset/17595
I had the same issue with he_IL – with project 3.1 and 3.1x and revision HEAD gives me “3.1.2-alpha” as version. Releasing like this, even if you override the version number manually (enter 3.1.1) under version) would still release witg 3.1.2-alpha in version.php, and would show a bleeding update notice to all users.
Setting the revision to 17595 seems to solve this issue.
Hi there,
If you want to build a proper 3.1 version now, there’s no way of doing so via GlotPress, at least not that I am aware of. Is it perhaps now time to create a 3.1 tag there instead of using the development tag (which is already at 3.2 bleeding alpha..) ?
I’m not aware of a way of doing it building from GlotPress either. Always use svn. Especially for 3.1 since the dist-files had a few changes.
Would love to build from GlotPress. Especially for the security-releases, since I would love an easy way to get around them plus there’s never (?) changes in the dist-files in those releases.
We have built the Brazilian Portuguese 3.1 using GlotPress.
One should use the Revision 17487, and the development tag.
The revision would get the correct code, and the development tag would get the strings.
(Most likely it will get some strings form 3.2, if already present, so having a 3.1 tag for strings would be a good thing.)
Please see an image here: http://gabriel.ppgr.com.br/wordpress/building-wordpress-3-1-package-from-glotpress/
I’m not sure if there might be a confusion or not: no 3.1 shows up on the first dropdown because it pulls those values from the repository. Hence, if no branches/3.1 or tags/3.1 exist, no 3.1. Those folders are *not* created automatically, translators with svn permissions must create and populate them themselves. Is this the problem?
No, it’s not that we can’t select the proper tag or branch, because yes, we can fix that ourselves, but that we can’t select a 3.1 translation from GlotPress. Only development and the old 3.0.x translatations. When I do select development it will actually create a 3.2 bleeding alpha with the translations from the development segment of GlotPress.. Hope this makes it more clear.
Got it. There’ll be a “Development (future 3.2)” very soon in GP and 3.1 will move to stable.
Awesome, thanks!
I created the GlotPress projects and now the 3.0.x project shows up in the package builder. Enjoy
You mean 3.1.x ?
Yep, Nikolay meant Project: 3.1 and 3.1.x.
Hi guys,
Could you please add jekrikken as a validator for the Dutch BuddyPress translation?
We can.
There’s just no limit to your awesomeness, is there?
Thanks!
There isn’t.
I am so lucky to have met you IRL then
You are
We are getting hammered with spam on the Dutch forum the last couple of days, is there something someone can do about it? Not sure if this is the best place to ask for help, but please point me in the right direction
I’m afraid you’ll have to keep spam/bozo/blocking them until either Akismet or they learn…
LOL… zh_CN also needs your help, but not on spam! http://wppolyglots.wordpress.com/2010/12/02/hi-there-i-think-i-need-more-privilege/#comment-1196
Thanks.
if that’s what it is, than that’s what we’ll do. What is the best solution, just deleting, blocking them of bozo?
How do others handle this? Currently I use the solution to ‘delete’, should we also block them or make the bozo’s?
block, bozo and delete them. In that sequence.
I *really* hope Akismet is learning FAST, because them spammers are not :/
Done. (tag it “request” next time, so that I get an immediate alert)