Libin Pan

Welcome!

Please click the links below to try it. Enjoy!

Thanks, Dave!

I just take a look on your blog. Your implementation looks great!

I really like your idea about Facebook and twitter. 500 characters limit sound perfect for these shout wall posts or status.

I was thinking use uOGT in another day, but found my website will be soon rejected by Google Translate Service. This AJAX one really helps!

Request for adding into WordPress Plugins List has been approved today. So please download from
http://wordpress.org/extend/plugins/google-ajax-translation/

And all the new changes will go there too.

Thx!

Thanks Phoenix!

To enable fulltext translation, mine may not be a perfect solution at this moment. As Google limits 500 characters for every request.

But you still can give a try:
Uncomment line 79 in ajaxtranslation.php

If you want to have a more professional one, please give a try on:
http://wordpress.org/extend/plugins/global-translator/#post-2877

This is the best one I’ve found so far. But too bad it is not free.

Thanks Sean!

The problem has been fixed. Please download from wordpress for the new version and overwrite your exist one.

Please feel free to let me know if it works for you.

Yeah, the plugin is only for WordPress. But the AjAX Language API is not.

I am not really sure about how you want to make it wok on localhost.

The AJAX Language API is a AJAX wrapper for Google Translate Services. If you want to use it, you need the access to the Google servers, which means you need to be online.

As long as you have internet access, it doesn’t matter you call it from your hosted server or your local machine. It should work.

Hi Rama,

Your idea sounds very interesting! Put internationalization into chatting is absolutely a great feature. But I am afraid that you may need a translate services inside your internal network if you want to make it work without internet access.

Some professional translation companies have this kind of software. But I believe the price will be way more higher than what we expect.

Hi David,

Your blog looks very beautiful!

Let me tell you what plugin does for translation. When the user click “View Post/Comment in ??? Language”, plugin will get the innerHTML of the current post/comment, then filter out all the html tags, such as
< p >, < a href=..>,
then send the pure text to google and wait for the translated result.

The reason for filtering html tags out is: if you send them within your text, google will translate the words inside of tags and return it back. Which will mess up the whole page.

I am trying to find a better solution for this, but no lucky yet.

Thanks Clementtang!

I am working on the next version now, which will have the options for choosing languages, but for now, you could just edit wp-content/plugins/ajaxtranslation/ajaxtranslation.php.

From line 46 to 58, remove anyone you don’t want and it should work.

Let me know if you have problem.

Thanks so much, loewez!

The problem is in the theme what I am using now. It was missing one line which is very important:
< ?php wp_footer(); ?>

I’ve added it back. So the translation plugin should be working again.

You are more than welcome!

You may notice this already, the translation plugin does work on Admin/Comments list too.

Looks like it is the same problem as I had. Could you please let me know what theme you are using, or you can just open :
…/wp-content/themes/your current theme/footer.php
Try to find if it has
< ?php wp_footer(); ?>

If not, please just add it in before < / body >
Hope this will fix the problem. Let me know if it still doesn’t work.

OK. It’s my fault.
Please remove the space between < and ?.
The line of code is:
< ?php wp_footer(); ?>