From GTranslate: Unable to perform Translation:Suspected Terms of Service Abuse. Please see http://code.google.com/apis/errors

I think I'm getting spanked for a lack of Google attribution. Would be cool if this module provided it.

Comments

seg108’s picture

Category: feature » support

I found this. Can you please guide me how to implement it for both node/add and node display? Thanks.

http://code.google.com/apis/ajaxlanguage/documentation/#Branding

- Changing from feature to support request.

spacereactor’s picture

2 questions.
1.) Have you import the GTranslate.php file? You have to manually upload the file into gtranslate-api-php folder. Inside i18n_auto there is README.txt for instruction and download from http://code.google.com/p/gtranslate-api-php/downloads/list

2.) what language are you try to translate? If you translating Chinese, Hebrew or Norwegian you have to add patch. see http://drupal.org/node/724194

seg108’s picture

Version: 6.x-2.x-dev » 6.x-2.0

Thanks for your reply.
Correction, I am using Auto draft translation 6.x-2.0 (aside: confusing that name in modules list is different to i18n auto translate).
Everything set up and working fine for a few weeks, but without any attribution displayed. Languages: English, Estonian, Finnish.
Is attribution included in dev version? If yes, are there options both for node create and node display?
Thanks.

spacereactor’s picture

The currently 6.x-2.x-dev doesn't port cck and taxonomy data to translated node, only title and body is port over with translation. There is a patch to clone node first, see http://drupal.org/node/759214 but still only the node TITLE and BODY can be translate with this patch. Plus there is a limited content that can be translate. if i not wrong, you can't translate more than 1500 characters.

seg108’s picture

I'm not sure we are on same page with this.
Google's Terms for Language API are here: http://code.google.com/apis/ajaxlanguage/terms.html
I simply wish to display the required Google attribution at node/add and node display.
See Branding and Google Attribution: http://code.google.com/apis/ajaxlanguage/documentation/#Branding
And examples: http://www.google.com/uds/samples/language/branding.html

greg.harvey’s picture

Title: Google attribution » Module needs to provide a block for Google attribution and README notes about its use
Assigned: Unassigned » greg.harvey
Category: support » bug
Priority: Normal » Critical

Thanks for flagging this. I think it's a bug report. If *not* showing the Google brand results in the API being throttled then that's a show-stopper! Until this is fixed, people should follow the link seg108 posted and include the code in a block to display on their site:
http://code.google.com/apis/ajaxlanguage/documentation/#Branding

seg108’s picture

Can you bring this right down to the layperson level? i.e. describe more precisely how to use the code provided by Google.
Thanks very much.

greg.harvey’s picture

Follow the link you posted and click the "view example" link underneath:
http://www.google.com/uds/samples/language/branding.html

View source, copy and paste the bits you want to a new block in Drupal with the input filter set to Full HTML so it doesn't strip out the <script> tags.

seg108’s picture

Thanks. And this part...

// attach a "powered by Google" branding
<div id='branding'> </div>
...
google.language.getBranding('branding'); 

...goes?

greg.harvey’s picture

It's all in the sample page. It all goes in the block. Just copy and paste from the sample page as is and delete the divs you don't want.

seg108’s picture

Thanks. I'll keep playing with this.

Correction to earlier comment:
Attribution unnecessary for node/add, really only needed for node display.

greg.harvey’s picture

Status: Active » Fixed

New block provided in 6.x-2.x-dev for 'Powered by Google' branding - users may position it as they wish to avoid breaching Google terms of service. There is also CSS and a theme function provided, should you wish to alter the branding block.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.