This plugin is guaranteed to drive more international traffic to your site by providing high quality translation, and SEO of your translated content.
Most of the other translation widgets and plugins, like those that are powered by Google and Microsoft, provide on-the-fly translation of your blog content. This has two negative aspects: first, the translation that your reader sees is raw machine translation which is known to be of questionable quality. Second, the content is not indexed by the search engines, which means that readers can not find your translated content on search engines and you lose out on valuable search engine traffic.
The GTS plugin provides human translation quality which is far superior than the other plugins. And the translated content is cached on the same server that your blog is hosted on. Search engines will index your translated content and your blog will come up on keyword searches. This will drive more traffic to your blog.
Translation is a 2-step process. In the first stage, your content is translated by our own machine translation server. Then, the translated content is edited by human translators who review the machine translation and make the necessary linguistic corrections. After the content is edited, a moderator reviews the content again to verify that it meets quality standards. Once the moderator approves the translation, the post goes live on your blog.
You have two choices: you can use your own people to do the human editing, or you can use the GTS community.
If you have associates that are qualified to edit the translation, or if you yourself are proficient in another language and can edit your own translation, then you can control the process yourself through the GTS Plugin Admin panel. This Admin panel allows you to assign Editor and Moderator priviledges to your own network of people so you can keep the process in-house.
Or, you can have the work done by the GTS community which is a worldwide network of hundreds of translators and language experts.
No. Comments are are passed through as-is.
We're continually adding new languages, so for the latest list, click here.
By default, the translated blogs will be accessed in subfolders of your main blog URL. So for example, the French language blog will be accessed via http://blogname/language/fr. The Spanish language blog will be accessed via http://blogname/language/es. And so forth.
If you want to assign your foreign language blogs to a subdomain or a TLD (Top Level Domain, like blogname.fr), you can do so by making the apporpriate configuration settings on the GTS Plugin area of your WordPress Admin panel.
UTF-8 only. Note that WordPress is configured to use UTF-8 by default. If you require another character encoding, please send a feature request.
When you publish a post in WordPress, our plugin will send that content onward to GTS. When we receive it, the content will be immediately passed through our machine translation software. Then, it will become available for our crowdsourced editors to begin the post-editing process. They will improve the quality of the translated content, after which, crowdsourced moderators will review the improvements. When the translated text is ready for prime time, one of the moderators will approve it, and the human-translated post will be sent back to your blog.
Additionally, when you first sign up with us, our system will pull in some additional information. In order to get your translated blog looking good from the get-go, we do an initial translation of all your blog's tags, categories, pages, and the posts that appear on your blog's home page.
Before the translated content is approved, it is stored on a staging area on our own secure servers.
Once the translated content is approved by a moderator, it is stored on your own server in your WordPress database. We'll also keep a copy in our database in case the moderators or editors decide to make more changes.
This happens when the data is stored in MySQL with the wrong character encoding. Execute the following SQL (being sure to replace 'wp_' with the prefix specified in wp-config.php if you've changed that value):
ALTER TABLE wp_gts_translated_options CONVERT TO CHARACTER SET 'utf8'; ALTER TABLE wp_gts_translated_posts CONVERT TO CHARACTER SET 'utf8'; ALTER TABLE wp_gts_translated_terms CONVERT TO CHARACTER SET 'utf8';
Then get in touch with us so that we can help you reload your content.
In order to work correctly, translations to Chinese require plugin version 1.1.6 or greater. Version 1.1.5 will translate your posts, but won't properly display them. Upgrade using your WP Admin panel, and you'll be good to go.
Please see the Virtual Host Setup section in the Other Notes tab.
Your WordPress theme is made up of a series of PHP files called templates.
If you are using theme translation, these links should be handled automatically. Otherwise, you're probably using the
echo home_url('/') with
Unfortunately, translating PHP source files correctly is tricky business and doesn't always work correctly. If you have translated your templates and want to revert to the originals for your translated blogs, untick the "Use translated templates" checkbox on the GTS configuration page.
Like above, it's tough to sort out what should be translated. Plus, there are probably random English text strings embedded in the PHP source, function arguments, etc. In order to get the most out of template translation, try these tips:
__function or its variants e.g.
random_php_method(__('hello')). IMPORTANT this only works for single-quoted arguments. recognized functions are:
Some english language text comes from deep down in WordPress' code, so you probably won't be able to get 100% of the text, but you should be able to get the lion's share taken care of.
There is a maximum entry size of 256KB...roughly equivalent to 75 pages of single-spaced text. Have you run into that limit?
Unforunately, yes. Here is a list of plugins that cause problems with the GTS Plugin:
This list is a work in progress and may grow as we roll out to more users.
Please see the Security section in the Other Notes tab.
Requires: 3.0 or higher
Compatible up to: 3.4.2
Last Updated: 2012-8-23
0 of 2 support threads in the last two months have been resolved.
Got something to say? Need help?