Opened 18 months ago

Last modified 7 months ago

#170 new defect

Remove links to Google Translate

Reported by: vanillalounge Owned by:
Priority: major Milestone: 1.0
Component: interface Version: 0.1
Keywords: 2nd-opinion has-patch dev-feedback Cc: nbachiyski, juanramondiaz, zodiac1978@…, dimadin

Description

The 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

Attachments (3)

helper-functions.diff​ (623 bytes) - added by vanillalounge 18 months ago.
translations.diff​ (792 bytes) - added by vanillalounge 18 months ago.
remove_google-translate.diff​ (27.6 KB) - added by juanramondiaz 13 months ago.

Download all attachments as: .zip

Change History (15)

vanillalounge — 18 months ago

vanillalounge — 18 months ago

comment:1   GDragoN — 17 months ago

Button shouldn't be removed, it should be fixed so that uses API V2 version:
​http://code.google.com/apis/language/translate/v2/getting_started.html

comment:2   petervanderdoes — 16 months ago

  • Keywords needs-patch 2nd-opinion added

As Google Translate API v2 is now available as a paid service only I think the button should be removed and when possible, be added as a plugin feature.

On the note of removal, there's quiet a bit of code left after the patches that needs cleanup if it's decided to remove Google translate.

comment:3   nacin — 14 months ago

Thinking we should probably just tear it all out and leave it to a plugin to implement it.

comment:4   nbachiyski — 13 months ago

Removing it all seems like the best choice.

We can look at asking Google for comping us access, but this would be implemented on WordPress.org via a plugin.

comment:5   nbachiyski — 13 months ago

  • Cc nbachiyski added

comment:6   nacin — 13 months ago

We considered paying for it when it was originally discontinued. See ​http://wppolyglots.wordpress.com/2011/12/18/translate-from-google-did-it-get/.

When we go ahead and remove it, we should try to add hooks and turn it into a plugin in the process.

comment:7   juanramondiaz — 13 months ago

  • Cc juanramondiaz added

I agree. I've just removed all the references to Google Translate. I attach the diff file.

juanramondiaz — 13 months ago

comment:8   zodiac1978 — 13 months ago

  • Cc zodiac1978@… added

Could Microsoft Translator be an alternative for Google Translate? Or an option/other plugin?
See: ​http://www.microsofttranslator.com/

comment:9   GautamGupta — 13 months ago

I'd prefer tearing it out and if we do, we also need to close down #133.

comment:10   c_schmitz — 12 months ago

Actually I'd rather not have torn it out. Rather upgrade it to Google Translate API 2.0 and deactivate it by default.

comment:11   sushkov — 7 months ago

  • Keywords has-patch dev-feedback added; needs-patch removed
  • Milestone set to 1.0
  • Version set to 0.1

Relevant #103.

comment:12   dimadin — 7 months ago

  • Cc dimadin added

I'm against removing since there is already working code and it won't be easy for a plugin to implement it.

Instead, I would display & load all Google Translate stuff only when API keys are set (inspiration taken from @Nightgunner5 patch on #103). That will make it easy for projects that want to use it to easily turn it on.

Note: See TracTickets for help on using tickets.