Bens Translator – Wordpress Plugin

Bens Translator is a Wordpress Translator Plugin. It uses Google Translator to translate pages and save a cached version to be displayed to your visitors. This allows the translated versions to be indexed by search engines something the “official” google translate does not. Bens Translator can increase you google traffic in other languages.

Features

Translates in languages allowed by Adsense
Caches pages to allow for search engine indexing
Configurable layout, Choose from Tables or DIVs to show the translation widget
Use google translate, for the most accurate automated translation
Adds a language code to your permalink structure for seperate navigation www.mysite.com/about becomes www.mysite.com/de/about
No databse modifications. The cached pages are saved into a directory for fast access and easy backups
Translate into the following languages
Italian, Korean, Chinese (Simplified), Chinese (Traditional), Portuguese, German, French, Spanish, Japanese, Arabic, Russian, Greek, Dutch, Bulgarian, Czech, Croatian, Danish, Finnish, Polish, Swedish, Norwegian, Hebrew, Serbian, Slovak, Thai, Turkish, Hungarian

Download

Download Bens Wordpress Translator

Quick Links

Changelog

Install Guide

Help Guide/FAQ

Donate

If you like this plugin and find it useful, help keep this plugin free and actively developed by clicking the donate button.

Global Translator Pro is released under this license by-nc-sa 2.5
Bens Translator is released under this license by-nc-sa 3.0

Trackbacks

310 Comments (Newest on top)

GG says:

14/01/2010 at 7:10 pm

Hi Ben, you’ve made some great progress! We’ve almost got it working now on our site. There seems to be one last, strange problem. The first time we click on, say the Korean flag, the page shows nicely in Korean. But if we refresh the page, or click on the Korean flag a second time, the translated portions of the page turn into garbage characters. For example: ëë° ìë – ê¼ ì¬ë ìºë ë¸ë¡

Reply
- Ben says:
  
  14/01/2010 at 11:55 pm
  
  Try turning off compression in the settings. You host may not handle it correctly
  
  Reply
  - GG says:
    
    15/01/2010 at 1:11 am
    
    Good thought, but no. Compression has never been set. No other compression or caching plugins are running. Seems to be only happening with the Asian fonts sets, not the Western sets. When I refresh the Italian page, it’s fine. When I refresh the Korean or Chinese pages, they become garbled.
  - Ben says:
    
    15/01/2010 at 3:37 pm
    
    I have my site’s main page translated to Korean (was translated by the newest version of the translator) and it doesn’t appear to do it for me, perhaps it is a browser issue? What happens when you refresh my site’s Korean page? http://www.techgremlin.com/ko/
    
    By the way the validation engine appears to be working great for me, it was a great feature to add.
  - GG says:
    
    15/01/2010 at 7:53 pm
    
    Hi Ben, your Korean page looks great. It displays properly on my browser. However, all of the Asian language pages on our site are having problems, regardless of which browser I view them from. They are fine at first, but if they are refreshed or retranslated, they turn into garbage. Interesting, if I take a newly translated page (one that is still working right) and submit it directly to Google Translation, bypassing the plugin, Google also turns the page to garbage. So I think WP is either corrupting the page when it serves it to Google, or the Google Translator is encountering something in the page that is making it go awry. Odd that is it only happening to the Asian fonts.
    
    If I take the source code of a newly translated page, and make a separate page out of it and save it on my desktop, it looks fine and refreshes fine. So there is nothing wrong with my browser.
- GG says:
  
  02/02/2010 at 4:59 am
  
  Ben, I have an update on that problem with the Asian characters displaying as garbage. I’ve been working with a technician at HostGator and determined that this line of code in the served page the issue:
  
  Currently, this line of code is appearing AFTER the code that displays the flags. When this happens, the Asian characters are displayed as garbage.
  
  If this line of code is moved up the page, just under the “base” tag, the Asian characters display correctly.
  
  The problem is that this line of code doesn’t seem to be explicitly stated in the header file, it appears to be dynamically created by something, so I can’t seem to control where the line falls vis-a-vis the flag code.
  
  I’m currently experimenting with explicitly stating that charset instruction just before the title tag. I’ll let you know how that turns out.
  
  Reply
  - Ben says:
    
    02/02/2010 at 10:22 am
    
    Can you email me the code that is causing the problem.
Andre says:

22/01/2010 at 7:36 pm

Hi Ben,
Thank you very much for this amazing Plug-in!
I Also have the problem that the Bens Translator can`t create the Flag File´s, cause of permission settings…
I get this message when i click on the flags:

“Bens-Translator has detected a problem with your filesystem permissions:
The cache dir
/var/www/web345/html/rcauto/wp-content/ben-translate-cache/current/it
cannot be read or modified.
Please chmod it in order to make it readable and writeable.(755)”
Permission is set to 755. I also tried 777 but it did not fix the Problem…
My site is: http://www.rc-autos.com
Hope someone can help me, can`t await to get it running! It`s awesome!!!

Reply
Frank says:

24/01/2010 at 12:13 pm

Hi Ben,
thanks for your work, but I have some trouble with the plugin. When I click a flag it appears the following message:

This page has not been translated yet.
Please click below for a semi-automatic translation.

In the cache directory the language folders appear, but there is nothing in. WP2.9 BensTranslator 1.6.1

Have you any idea?
Thanks for help
Frank

Reply
Tobias says:

24/01/2010 at 3:13 pm

I get this error.

# Translations status:Bad or unhandled response from the ‘GOOGLE’ translation engine. This could mean that:

* Your blog has been temporarily banned: increase the time interval between the translation requests and wait for some days or switch to another translation engine
* The translation engine is currently not responding/working: wait for some days or switch to another translation engine
* The translation engine has changed something (i.e. the translation url): wait for the next release of Bens-Translator
* You haven’t added the flags widget on your pages: adding the flags bar is mandatory in order to make Bens-Translator able to work correctly

How should i fix it to get it work?

Reply
- Ben says:
  
  25/01/2010 at 4:12 pm
  
  The above error message is quite descriptive.
  If you are on shared hosting try increasing the connection interval.
  If google has blocked you this can take 1-2 days to clear
  
  Reply
  - Tobias says:
    
    25/01/2010 at 4:21 pm
    
    No i dont share host wit some one.
    
    I haw increasing the connection interval to: 1200
    
    I hope it sone work.
  - Tobias says:
    
    26/01/2010 at 4:05 pm
    
    I am still bannad and it has gone 2 days now.
  - GG says:
    
    26/01/2010 at 7:19 pm
    
    We have the same message now “:Bad or unhandled response from the ‘GOOGLE’ translation engine”. I had been doing a lot of testing and troubleshooting, and I fear that Google may have interpreted that activity as an autobot. So I disabled the plugin for a couple of days, and then re-abled it with a 1025 interval. Google is still not translating any of our pages. Is the ban permanent? Is there a way to change the translation engine from Google to one of the others?
GG says:

28/01/2010 at 7:13 pm

Hi Ben, I have new and interesting info on this problem! Maybe this will help us nail it down…

When I used my browser to view the page source of the garbage page, I saw all the garbage characters and incorrectly assumed the page was also written on the server that way. It isn’t! When I go to the server and edit the page directly, the Asian characters are displaying correctly. So the static page on the server seems to be correct, but something is happening when the page is served up and it’s getting scrambled. I get the same results if I use different browsers, different computers, and even different IPs. The first time it displays the static page, it shows fine, but every time after that it’s garbage (with the Asian pages). There are no entries in the PHP error log. Here’s a snippet from the plugin’s debug log, which looks fine I think:

2010-01-28 17:37:27 [from: 11.11.11.11|Mozilla/5.0] – Bens-Translator Initialized
2010-01-28 17:37:27 [from: 11.11.11.11|Mozilla/5.0] – Permalinks on
2010-01-28 17:37:27 [from: 11.11.11.11|Mozilla/5.0] – Generating Rules
2010-01-28 17:37:27 [from: 11.11.11.11|Mozilla/5.0] – Loading Page:
2010-01-28 17:37:27 [from: 11.11.11.11|Mozilla/5.0] – bentr_get_page_content :: returning cached version (_blog_ko) for url:http://mydomain.com/blog/ko/

[We are still prelaunch so I have altered the ip and domain name here to protect privacy].

If I take the source code directly from the static page, and copy it into any non-html application (like Word or Notebook), the Asian fonts turn to garbage. But if I copy the code into an html editor, the fonts are preserved and I can make an html page on my desktop that I can refresh repeatedly without losing the Asian fonts. This makes me wonder if my WP pages are going through some sort of non-html process as they are being served up to the browser, and that could be scrambling my Asian fonts. I’m reaching here, obviously. I’m sure you will have better ideas!

I don’t have compression on. I’m not running any compression or caching plugins.

Reply
- Ben says:
  
  29/01/2010 at 9:24 am
  
  Can you email me the page from the cache.
  and the page saved from when you view it in your browser.
  
  Reply
Ian says:

29/01/2010 at 2:49 am

Dear Ben and Team,
I had so many problems with Google Translator that I am giving a shot here with yours. The major problem I have though is that you don’t offer a flag for Brazil as an option in your translations. Could you please make that adjustment as the people viewing my site are 90% Brazilians and asking them to click on a Portugal flag is kind of offensive. Thank you in advance for your consideration.

- Ian

Reply
- Ben says:
  
  29/01/2010 at 9:25 am
  
  You are more than welcome to change the picture yourself,
  It is very easy to overwrite in the pictures folder of the plugin.
  It will be too complicated to maintain multiple pictures for each language
  
  Reply
  - Ian says:
    
    29/01/2010 at 9:48 am
    
    is that in on my host on in Wordpress?
    
    Thank you,
    Ian
Scott says:

30/01/2010 at 12:29 am

Thanks Ben for the plugin, though the code seems to have W3C-related errors. It seems there are 2 errors per translation sequence:

1. Error: ID “translation_bar” already defined
2. Error: ID “flag_’country code’” already defined

On another note, how can one get Adsense to work with translated pages? Once a page is translated, it seems Adsense does not know what to show? Will Adsense act differeently in the target country?

Reply
ABDL86 says:

30/01/2010 at 4:30 pm

This not working for mi: New page showing what pages are translated

What should i do?

Reply
Svard says:

30/01/2010 at 8:27 pm

Plugin could not be activated because it triggered a fatal error.
Fatal error: Call to undefined function: interface_exists() in /web/u/busin/wp-content/plugins/bens-translator/core/functions.php on line 69

What could bee wrong?

/Svard

Reply
ABDL86 says:

01/02/2010 at 4:59 pm

Hi

http://www.alltomabdl.se/blogg/en/

Why are the pages translated so strange?

Reply