Comments on: Google Translation Tip

By: Sigonrong Dari Gua Hiro

Sigonrong Dari Gua Hiro — Wed, 17 Aug 2011 19:32:57 +0000

I tried to make my own plugin consisting only both code above. Then I noticed that javascript was added at the bottom of my site. But, all pre and code are remain changed by google translator. (sorry for my bad english)

By: philippe | photofloue

philippe | photofloue — Mon, 06 Jun 2011 22:33:55 +0000

Thanks Otto for the original article, and for this tip on automatic translation.
As Willem mentioned (merci !), I thought Google was doing OK on that translation job — except for code, but that is fixed now.

By: Aldo

Aldo — Sat, 04 Jun 2011 07:17:59 +0000

Good job, Alex! Now the code wrapped in SHE shortcodes isn’t translated anymore by Google. Thanks!

By: Alex (Viper007Bond)

Alex (Viper007Bond) — Fri, 03 Jun 2011 23:10:27 +0000

Please upgrade to the latest version of my plugin and then visit it’s settings page. It allows you to select which version of the Javascript highlighting package you want to use, either v2.x (the one you’re using now) or v3.x (the one you don’t like). The plugin has received new features and bug fixes in the versions since the one you’re using now.

Also I’ll add this to my plugin. Thanks for the tip!

By: Willem

Willem — Fri, 03 Jun 2011 12:59:06 +0000

Actually Philippe Durand, the author of the post in question, said that the automatic translation by Google was NOT bad. He also mentions your blog as indispensable for people interested in WordPress …

By: Aldo

Aldo — Fri, 03 Jun 2011 05:46:05 +0000

Otto, I can assure you that it works well!
So this means that Google process the page after the javascript has made those changes.

OT
FYI, I didn’t receive any email from your subcription manager. I checked my spam box and has no email from your domain.

By: Otto

Otto — Thu, 02 Jun 2011 17:06:37 +0000

I kinda doubt that would actually work. I don’t think Google is doing the translation bit after processing the Javascript. I think it’s reading the actual HTML and modifying it before that happens.

By: Aldo

Aldo — Thu, 02 Jun 2011 09:54:02 +0000

Thanks for sharing this, Otto.
I would share a tip for adding the class “notranslate” to some elements via jQuery.

Let’s say we want to add this class to these “not-to-be-translated” elements: code, pre and any element with “.code” class.
Let’s start.

1. Add these lines to your functions.php file:

wp_register_script( 'googlenotranslate', get_stylesheet_directory_uri() . '/js/google_no_translate.js', array( 'jquery' ), false, true );
wp_enqueue_script( 'googlenotranslate' );

2. Create a new file and paste this:

jQuery(document).ready(function($){
	$("pre").addClass('notranslate');   // Targets PRE elements
	$("code").addClass('notranslate');  // Targets CODE elements
	$(".code").addClass('notranslate'); // Targets ANY element with .code class
	// Add other elements or class or ID here
});

3. Save this file with the name “google_no_translate.js” and put it in a subdirectory “js” of your theme directory.

You’re done.

Obviously, if you’re using a custom plugin for all your custom functions, you’ll modify that file instead of the functions.php file. This will preserve all your custom features, even if you’ll change your existing theme.

I’m not a jQuery expert, so I wonder if those three lines with ‘addClass’ could be written in one line only.

By: franck

franck — Thu, 02 Jun 2011 07:17:59 +0000

Thank you,
from a french.