707190 - Google Translate Error into localize.mozilla.org

Status: RESOLVED INCOMPLETE

(Webtools Graveyard :: Verbatim, defect)

Description

[Bogomil Shopov[:Bogomil]]

1. Log in to your account
2. Try to auto-translate a kewyword by pushing little G icon:

This error appears:
Please use Translate v2.  See http://code.google.com/apis/language/translate/overview.html

Comment 1

[Friedel Wolff]

Support for version 2 of the Google API has already been implemented in Pootle, and will form part of the release of Pootle 2.2.

Comment 2

[Axel Hecht [:Pike]]

Is there an upstream ticket that you can add to the "Bug URLs" here?

Also, is there a timeline for 2.2? That'd be useful to know.

Also CCing Peter and Laura, which codebase are you working on with the sign-on stuff?

Comment 3

[Vito Smolej]

note that google translate v2 is a not-for-free service (http://code.google.com/intl/sl/apis/language/translate/v2/pricing.html). Is Mozilla getting a special deal on it? I pretty much doubt it. Has this cost been budgeted and accepted?

smo

Comment 4

[Dwayne Bailey]

Added upstream bug.

We're working towards 2.2 just need some more planning before we know a release date.

But generally this bug is moot if Mozilla aren't planning to pay for translations.  In its current implementation anyway.

Comment 5

[iwofox]

(In reply to Dwayne Bailey from comment #4)
> Added upstream bug.
> 
> We're working towards 2.2 just need some more planning before we know a
> release date.
> 
> But generally this bug is moot if Mozilla aren't planning to pay for
> translations.  In its current implementation anyway.

Yes, can't agree more.
After one more year of planning, what plan we got now is my great wondering.

Google wanna get paid for their tooltip trick and it's a bad olds(not news) for Mozilla Verbatim. It seems both side will change their mind or budget Never Ever.

But what is important and good here for our contributors has been seen for nothing in too much days.

What if we just remove the Google translate toolbutton from that box, and suggest volunteers to use some GreaseMonkey scripts instead. Google translate is still free for end-users(In fact our contributors have done in this way).

Why did we still hold that poor dead quad-colored belt g button(for memorial a lost wife!?) and make more confusing？

That's my plan, thank you!

Comment 6

[Vito Smolej]

(In reply to Dwayne Bailey from comment #4)
> Added upstream bug.
> 
> We're working towards 2.2 just need some more planning before we know a
> release date.
> 
> But generally this bug is moot if Mozilla aren't planning to pay for
> translations.  In its current implementation anyway.

Hi Dwayne: 

I have a subscription to Google translate V2 and would be ready to chip in my own money, if given the possibility (by providing the necessary ID etc, whatever Google requires) to open the channel. 

I guess this could turn into quite a hairball - on the Mozilla side I suspect. So do not try to hard (g) - there's not many "cheapos" like me around here  and I can do it all off line anyhow, for instance in OmegaT. 

Just thought it would be worth mentioning.

Regards

Vito