Extension talk:Google Translator

Subversion
Can someone help me getting the files on the SVN server thing? I tried, but I keep getting access denied (403) errors.
 * You mean on Wikimedia's SVN server? See Commit access requests, though it would be better if you published your code on-wiki first for public review. Max Semenik 16:08, 17 June 2010 (UTC)
 * Code is published, I will request access at a later stage, thx for the info though Joa ds 16:18, 17 June 2010 (UTC)
 * Neat, I made a couple of minor corrections. Max Semenik 16:47, 17 June 2010 (UTC)

replace toolbar?
hi, your extension works wonderfully and the way it fetches the translated text with ajax is like a magic! My only concern is that the toolbar may be disturbing. This toolbar is exactly the same as the translation toolbar in Google Chrome, and it's been one of the most "disliked" functions in Google Chrome User Forums. Some similar toolbars are placed at the bottom and make it lesser disturbing. While I have totally no idea about the google ajax, is it possible to move the toolbar? --Wmama 19:47, 30 September 2010 (UTC)
 * It is indeed calling the translate bar, but you can switch it off for certain webpages as you desired, so shouldn't be much of a problem--Joa ds 21:58, 17 August 2011 (UTC)

Showing the Translation Box On-Demand
I'm using the CustomNavBlocks extension to control my sidebar, so Translator box doesn't show up on its own. How do I get it to display on a page? Thanks --Skew 18:33, 24 February 2011 (UTC)

Using with MW 1.18.0
I installed Google Translator on my wiki and had no problems with it other than formatting. The toolbar stuck out into the page (using Vector) when I used it with a blank list of languages to get all languages. The problem is the entries "Chinese (traditional)" and "Chinese(simplified)" make it really wide. So I went to the Google toolbar configuration tool, selected all languages, then got rid of the two Chinese ones. Now I have almost all the languages and a toolbar that fits in the sidebar (sorry, China; only a billion people I'm ignoring).

The other problem was the branding "Powered by Google Translate" under the toolbar was sticking into the page. I fixed that with some CSS to wrap the text around the Google logo. At Google there is an option to show just the toolbar without the branding (has a little G badge), but it makes the toolbar wider. You could make this change to GoogleTranslator.class.php. I added the CSS for wrapping to the main article, but it is:

a.goog-logo-link img {display: block}

--Brted 16:17, 15 January 2012 (UTC)

Edit request
My pending changes are stuck - please remove the text I've added to the beginning of the Intro (ending with "Signed by HTFFanBrandon04"). HTFFanBrandon04 (talk) 05:03, 26 March 2012 (UTC)
 * I've accepted your revert of it, but I see no technical justification of it because this extension does not modify the database.Jasper Deng (talk) 05:15, 26 March 2012 (UTC)

Adding more languages
I need basically all languages. How does that code look?


 * In localsettings.php, just leave the list of languages blank like this and you will get everything:

Brted (talk) 11:19, 24 April 2012 (UTC)

Error with MW 1.21.1
I was getting an error about a function call. I found out that you have to go into the file GoogleTranslator.class.php and comment out the following line, which isn't necessary and uses a function that is no longer supported:

Brted (talk) 03:02, 18 June 2013 (UTC)


 * This fixed it for me too. I'm going to suggest we remove the line from the reference source code on Extension:Google_Translator.  As I understand it, this would mean burning support for MW 1.15 (see r52503) but that seems a fair exchange for adding support for 1.21+.  Objections, anyone? AL286 (talk) 15:32, 8 December 2014 (UTC)

Error in Mediawiki 1.23
While installing the extension on Mediawiki 1.23, I got the following error.

Fatal error: Call to undefined function wfLoadExtensionMessages in /u01/UAG/apache/htdocs/old_TCS_Rewardz_2.2/extensions/GoogleTranslator/GoogleTranslator.class.php on line 14

Solution - Comment "wfLoadExtensionMessages( 'GoogleTranslator' );" from the code. It did not have any impact on the translation.

HTTPS compatibility
Currently the extension has poor compatibility with SSL. In modern browsers, the user will get a security warning if it's used in an HTTPS page because it attempts to retrieve the Google Translate script over HTTP. Changing the script reference in GoogleTranslator.class.php to a protocol-relative one seems to work:

Does anyone have any objection to me making this change in the reference source on the article page for this extension? AL286 (talk) 12:55, 8 December 2014 (UTC)