The link “Translation from Google” in glotpress gives the following error since a couple of days
Error in translating via Google Translate: undefined!
The link “Translation from Google” in glotpress gives the following error since a couple of days
Error in translating via Google Translate: undefined!
Heads up translators, http://wpdevel.wordpress.com/2011/11/29/3-3-status-update/
…and keep an eye on http://core.trac.wordpress.org/ticket/19020, too 😉
I am getting the same problem with Sanskrit – sometimes 352 strings only. And then, from nowhere, boom! Thousands. Then, again, 352…
Please do something about the horrible cache function in glotpress! It takes a couple of minutes every time you need to log in. Not acceptable. Glotpress is already slow as it is.
Does this happen no matter which page you’re on when you click the Log In link? I haven’t been able to reproduce. Aside from the fact that translate.wordpress.org/projects/wp/dev/ is indeed slow (string counting needs a rehaul), all other pages feel normal here.
Usually I log in from http://translate.wordpress.org/projects/wp/dev/sv/default , but this happens on every page i try to log in from. It happens on 2 different computers with Win7 in Firefox 6 & 7, Chrome, and Opera.
Same behavior with the standard browser in Android.
I am also experiencing the same problem. I tried with Firefox (6 and 7) and Chromium on Ubuntu and with Firefox on Win 7. I need to refresh login page several times or click on previously unvisited link to get logged in.
Does clearing cache and cookies make it any better at all?
Only if I clear the cache and then visit the login page directly (without opening any other page at translate.wordpress.org), all pages will display as they should. Otherwise, if they were previously cached, they are always displayed as for non logged in users until I click on some link that I haven’t visited previously (for instance, I usually open some random page in translated messages).
No at all here
Any chance you could try to reproduce this on a local install?
I managed to reproduce the error by activating mod_expires on my server. I’m using Apache 2.2.21. I added this to .htaccess in the GlotPress’ directory:
ExpiresActive On
ExpiresDefault “access plus 1 week 1 hour”
After adding this code, GlotPress had the same caching issue as on translate.wordpress.org.
I got a local install of GlotPress where I can’t repoduce this.
Having a hard time logging in on wp.org (every site). I got the correct details but it seems some cache function is messing things up. If I refresh/hard refresh the page in question a bunch of times I’ll get in, but this is quite annoying. (Running FX6 and Chrome).
A correction, it doesn’t happen on the local site, but i does on glotpress.
Is it really just me having this problem? Really annoying in GlotPress I’ve tried different computers, different browsers, clean cache, same problem.
Got reports of wp-mail.php errors being displayed in English instead of installed language. Can’t see any errors in the sv_SE package, might it be a server specific problem or a global bug?
sv_SE uses SVN (not gp + /dist) when building packages.
Do you have any detail on what errors it is?
Maybe it is the POP3 error message.
Yes it is the POP3 error message.
Ok. Please could you open a core trac ticket for this and I will look into it.
I suspect it is a combination of the fact that some of the content of these strings isn’t translated and some of it uses _
instead of __
.
Will do.
bbPress project strings are not getting updated in GlotPress, something wrong?
Updated by hand, but no changes detected…
There are changes. I updated it myself from the POT @ http://svn.automattic.com/bbpress-i18n/pot/branches/plugin/ (not the usual POT I see).
http://bbpress.trac.wordpress.org/browser/branches/plugin/bbp-languages/bbpress.pot
(matches http://bbpress.svn.wordpress.org/branches/plugin/bbp-languages/bbpress.pot)
Maybe so, but it doesn’t match the one I linked to which is generated on a later date.
The strings in the GlotPress project doesn’t match the latest beta release, strings in the POT I linked to does.
bbPress’ php isn’t being harvested. Looking.
Updated manually from a fresh makepot.php run, 42 new strings were added.
Zé, can you setup Swedish for bbPress in GlotPress? Add me (damst) as a validator.
Darn, that didn’t get tagged correctly, should have been tagged request, sv_SE, bbPress
Done (and fixed the tags)
Thanks 🙂
Zé, is it just damst (me) who has validator access at wp.org for sv_SE? If not, remove everyone but me (damst) for the WordPress project. I’m the only one active.
There seems to be a problem displaying names with special characters on the credit page. The Swedish signs for åäö is shown as �
jobjorn, sebastian_d and mibbo96 were removed. I’m waiting for @nacin‘s feedback on all of the credits issues.
10x
Although, to be fair, the encoding issue sounds like a core trac ticket waiting to happen…
There was a core ticket for a similar issue that I looked into and @nacin referenced in the post here I believe.
It’s this one:
http://core.trac.wordpress.org/ticket/17487
Yeah. Turned out this was a different but similar issue 🙂
Encoding issue is now fixed in the api.
I believe that something you changed actually introduced a new issue with last character of my name (probably with other too but I don’t see them).
If my memory is good, around a week or more (which coincides with your comment) ago it was shown right in both translators and contributors to 3.2 lists. (sr_RS)
Is it just me, or is this solution of using a blog as a platform for polyglots getting ridiculous? If you want to be in the loop, you need to simply subscribe to both feeds (posts and comments) and at least skim through them. Not sustainable in the long run.
Come on, let’s run bbPress / BuddyPress @ wp.org!
I think BuddyPress is overkill, personally. I get your point re bbPress, though. Just the thought of having a [resolved] marker sends shivers of pleasure down my spine. The question is if, given a forum, a P2 is something we don’t need at all, such as general discussions and the like. I’m not going to second-guess the .org devs, but I’d say that even with bbPress, something like make.wordpress.org/i18n is still relevant.
BuddyPress might be overkill, but I like the idea of having groups per language team.
I wonder what are you missing in P2 that makes you want bbPress/BuddyPress?
For profiles, there’s always http://profiles.wordpress.org
First of the ability get the flow to be shown in the order of last updated thread first (which I think is essential for a discussion forum). Next, to get everything categorized, with P2 it’s getting very cluttered.
People are obviously missing stuff here, things doesn’t get resolved and so on. Once a thread is getting a few pages back the discussion dies, that doesn’t encourage open discussions at all.
The more people we get, the harder it becomes to keep up with the flow in P2.
+ 1. 🙂
Not to mention that http://profiles.wordpress.org points to .org profiles and this is a .com P2…
The process on making the contact form optional on local sites are……?
+4 months and nothing yet (https://wppolyglots.wordpress.com/2011/01/12/how-can-i-disable-the-contact-form-on-an/)
Since no one even seems to bother answering this, I simply removed the contact page. Really not a nice solution since the menu item is static and can’t be removed. A simple page without the actual form and plain text information on how to contact the language team would be the simple solution here.
I am getting a bit concerned about how requests/questions are (not) followed up here. In comparison to the mailing list, it’s getting worse when using a blog. You would expect people to whom it concerns to subscribe/getting e-mail notifications to follow up on requests/questions, which seems not to be the case. Only the first couple of posts are getting the attention needed.
Browse a few pages back and you’ll find a bunch of unanswered questions/requests. Maybe it’s getting too cluttered to use a blog like this for polyglots?
As more people are getting involved and active on polyglots, more cons shows using P2.
bbPress next?
Could you point me to any open requests? A post’s author normally gets notified of answers to his posts and there are always the options to subscribe to the blog or to follow-up comments. You do have a point re bbPress and possibly even BuddyPress.
Yup, those where two in a short time 😉 (your doing a great job, but I’m guessing it’s getting a bit harder following up on every request with this kind of layout)
Another one https://wppolyglots.wordpress.com/2011/01/12/how-can-i-disable-the-contact-form-on-an/#comment-1568 (kind of a request)
There are some discussions that kind of runs out of steam since there is no way really to bump a “thread”.
polyglots.wordpress.org (with bbPress/BuddyPress) ftw 😉
Re the contact form, I’ll look into making it “hideable”. As to the next solution for discussing polyglothings, let me bounce a few ideas with the wpdevel crew and come back with a proposal.
Update?
^ @ contact form that is
Not yet. It’s on the to-do list and I’ll start a new thread when we’re there
I thought it’s just me who gets that impression. :-S But please don’t get me wrong, it just seems that requests get pushed down the pages too early.
Well, the Burmese discussion certainly didn’t help, but I’ll increase the # of posts per page
We need a form of Notify.
Yeah, that would be cool. I might be a bit old-fashioned, but e-mail is probably the best way to go, even if it’s in the form of e-mail notifications.
My vote is still on BuddyPress. Would be a great way to collaborate in conjunction with glotpress per team basis (groups in bp).
Might be, but what about those who prefer to work over SVN (me :-))?
SVN wouldn’t go away. We still have those static files…
I hope so. Translating using web-based services isn’t my favourite idea.
Don’t get me wrong, I prefer using SVN too. But it doesn’t mean that you cannot make use of glotpress too. It’s for example a good way to get others involved and propose changes. And teams with more than one contributor probably finds it useful to collaborate translations with (even if you’re using SVN for the final version).
With something like BuddyPress we wouldn’t need to have internal team discussions cluttering other discussions. Contacting teams directly would be much easier, and so on. I can only see good things making use of BuddyPress in comparison to today’s solution.
I think those are separate discussions (i.e. svn and offline translating). Since you can export the .po, open it locally, update it and import it back into GP, the point about svn might be moot. That said, 3.2 will see a wider discussion regarding the bundling of languages. Stay tuned.
BuddyPress would be great! When I recommended P2 a while back, I just didn’t think that was a viable option… but if we can get that at something like polyglots.wordpress.org, that would be awesome… but just to be clear: we aren’t talking about transforming the entire locale.wordpress.org system, are we? Just turning this blog into a BuddyPress install with groups+bbPress activated (but not “buddy blogs”) …
Just turning this blog into a BuddyPress install with groups+bbPress activated (but not “buddy blogs”)
Yes. That was my thought. Not the locale.wordpress.org system. But I don’t know exactly what kind of ideas Zé are bouncing with the wpdevel crew. Maybe some even better idea comes out of it 🙂
I spoke with Zé about this a few days ago. We’re going to move this site to wordpress.org at some point in the near future, which should provide some extra flexibility in handling i18n requests. The initial step will be to add a simple “resolved” state to P2 for Zé.
The more resources we expend on reinventing a requests system, the longer it will take for other improvements on the roadmap, such as implementing language packs, so we can evaluate future options once we’ve tried basic modifications to the existing workflow, rather than a complete pivot.
I think that is taking it a bit to far. What needs reinventing? A simple change of platform is the request. Most of the concerns would get resolved by simply using BuddyPress instead. This blog into BuddyPress, no need to create new features right now.
BuddyPress out-of-box would do just fine. That’s really all that is needed for a much better solution than what we’re using here today.
Can’t be much of a hassle to simply setting up a bp install?
Whatever you decide, please make sure there’ll be a good e-mail notification system, OK? 🙂
I’ll start a new thread on this P2 as soon as I have a proposal, ok?
Sure. 🙂
Zé, please check https://wppolyglots.wordpress.com/2011/03/07/ze-can-you-create-sv-se-for/#comment-1639
Sorry about that. Done.
One more. Please add the user mibbo96 as a validator for WordPress for BlackBerry too. Thanks
This one fell through the cracks. Now done.
Thanks
Please add Swedish (sv_SE) to Jetpack, add the wp.com user eyesx as a validator. Thanks
Done.
Thanks
Zé, can you create sv_SE for “WordPress for Windows Phone”? Add the wp.org user damst as a validator. Thanks.
Done.
Thanks
Zé, can you please add the wp.org user mibbo96 as a validator too?
Ping @Zé
Ünsal Korkmaz 6:37 am on December 3rd, 2011 Permalink |
Google Translate API v1 was officially deprecated on May 26, 2011; it was shut off completely on December 1, 2011. http://code.google.com/apis/language/translate/overview.html
Mattias Tengblad 7:04 am on December 3rd, 2011 Permalink |
Ah thats right. Too bad, will considerably slow down the work flow in GlotPress 😦 Especially since gp doesn’t handle updated strings as efficient as poEdit.
Mark Thomas Gazel 8:50 pm on December 5th, 2011 Permalink |
That’s too bad. Can’t something be done? The paid version perhaps?
Rafael Poveda - RaveN 6:34 pm on December 6th, 2011 Permalink |
Losing the automatic google translation is not that bad IMO. A bit more work, a lot more quality in this work.