1 | === Global Translator ===
|
---|
2 | Tags: translator, multilanguage, automatic translator, google translations, babelfish, promt, freetranslations, widget
|
---|
3 | Author: Davide Pozza
|
---|
4 | Contributors:
|
---|
5 | Donate link: http://www.nothing2hide.net/donate_global_translator.php
|
---|
6 | Requires at least: 2.3
|
---|
7 | Tested up to: 2.8
|
---|
8 | Stable Tag: 1.2.5.1
|
---|
9 |
|
---|
10 | Automatically translates your blog in 34 different languages!
|
---|
11 |
|
---|
12 | == Description ==
|
---|
13 |
|
---|
14 | Global Translator automatically translates your blog in the following 41 different languages:
|
---|
15 | Italian, Korean, Chinese (Simplified), Portuguese, English, German, French, Spanish, Japanese,
|
---|
16 | Arabic, Russian, Greek, Dutch, Bulgarian, Czech, Croatian, Danish, Finnish, Hindi, Polish, Romanian,
|
---|
17 | Swedish, Norwegian, Catalan, Filipino, Hebrew, Indonesian, Latvian, Lithuanian, Serbian, Slovak,
|
---|
18 | Slovenian, Ukrainian, Vietnamese,Albanian,Estonian,Galician,Maltese,Thai,Turkish,Hungarian.
|
---|
19 |
|
---|
20 | The number of available translations will depend on your blog language and the translation engine you will chose to use.
|
---|
21 | Main features:
|
---|
22 |
|
---|
23 | * **Four different translation engines**: Google Translation Engine, Babel Fish, Promt, FreeTranslations
|
---|
24 | * **Search Engine Optimized**: it uses the permalinks by adding the language code at the beginning of all your URI.
|
---|
25 | For example the english version on www.domain.com/mycategory/mypost will be automatically transformed in
|
---|
26 | www.domain.com/en/mycategory/mypost
|
---|
27 | * **Fast Caching System**: new fast, smart, optimized, self-cleaning and built-in caching system. Drastically reduction of the risk of temporarily ban from translation engines.
|
---|
28 | * **Fully configurable layout**: you can easily customize the appearance of the translation bar by choosing between a TABLE
|
---|
29 | or DIV layout for the flags bar and by selecting the number of translations to make available to your visitors
|
---|
30 | * **No database modifications**: Global Translator is not intrusive. It doesn't create or alter any table on your database: this feature permits to obtain better performances.
|
---|
31 |
|
---|
32 | **Global Translator is the first real (and free) traffic booster for your blog!**
|
---|
33 | It can help you to reach a lot of new users and consequently to strongly increase your popularity: if you derive some benefits and if you want to support the development,
|
---|
34 | please consider to support me with a donation.
|
---|
35 |
|
---|
36 | For the latest information and changelog visit the website
|
---|
37 |
|
---|
38 | http://www.nothing2hide.net/wp-plugins/wordpress-global-translator-plugin/
|
---|
39 |
|
---|
40 |
|
---|
41 | **A Pro version with full support and additional features is also available!**
|
---|
42 | Learn more by visiting this page: http://www.nothing2hide.net/global-translator-pro/
|
---|
43 |
|
---|
44 |
|
---|
45 | == Installation ==
|
---|
46 |
|
---|
47 | 1. Upload the folder "global-translator" to the "wp-content/plugins" directory.
|
---|
48 | 2. Activate the plugin through the 'Plugins' menu in WordPress.
|
---|
49 | 3. From the main menu choose "Options->Global Translator" and select
|
---|
50 | your blog language and your preferred configuration options then select "Update Options".
|
---|
51 |
|
---|
52 | **How to upgrade**
|
---|
53 |
|
---|
54 | If upgrading from 0.9 or higher, just overwrite the previous version (don't delete the "cache" directory!!), otherwise uninstall the previous
|
---|
55 | version and follow the Installation instructions; don't use the automatic upgrade feature or your cache will be erased!
|
---|
56 |
|
---|
57 | Starting from 1.0.8 the cache directory has been moved outside the plugin directory in order to support the Wordpress automatic pluging update feature:
|
---|
58 | the content of the previous existing cache (inside wp-content/plugins/global-translator/cache) will be automatically and progressively moved to the new
|
---|
59 | cache location (wp-content/gt-cache) but, if you want, you can manually change the cache location by using your ftp client or a shell access.
|
---|
60 |
|
---|
61 | == Configuration ==
|
---|
62 |
|
---|
63 | If your theme is widged-enabled, just choose "Presentation->Widgets" from the administration main menu
|
---|
64 | and drag the "Global translator" widget on the preferred position on your sidebar.
|
---|
65 | If your theme is not widgetized, just add the following php code (usually to the sidebar.php file):
|
---|
66 |
|
---|
67 | <?php if(function_exists("gltr_build_flags_bar")) { gltr_build_flags_bar(); } ?>
|
---|
68 |
|
---|
69 | After this simple operation, a bar containing the flags that represents all the available translations
|
---|
70 | for your language will appear on your blog.
|
---|
71 |
|
---|
72 | == Frequently Asked Questions ==
|
---|
73 |
|
---|
74 | = The full translation process takes a lot of time. Why? =
|
---|
75 |
|
---|
76 | In order to prevent from banning by the translation services, only a translation request every 5 minutes will be allowed. This will permit to fully translate
|
---|
77 | your blog whithout any interruption; this message will completely disappear when all the pages of your blog will be cached.
|
---|
78 | Remember that this message will also appear if you're currently being banned by the translation engine: this could happen if for example your blog shares the
|
---|
79 | same ip address with other blogs using older versions of Global Translator.
|
---|
80 |
|
---|
81 | = "This page has not been translated yet. The translation process could take a while: please come back later." message when trying to access a translated page =
|
---|
82 |
|
---|
83 | Upgrade to 1.0.8 or later. Starting from 1.0.8, a browser asking for a not yet translated page will be warned and redirected in 5 seconds to the translation service
|
---|
84 | page in order to provide a temporary "backup translation service". Obviously, when the page is translated and saved on your cache directory, this redirection
|
---|
85 | will disappear and the translated and cleaned page will be served by your blog.
|
---|
86 |
|
---|
87 | = I have a Global Translator version prior than 1.0.5 and Google doesn't translate anymore! =
|
---|
88 |
|
---|
89 | Starting from 27th of August 2008, Google has introduced a block in order to prevent not human translation requests: just upgrade to 1.0.5 or later.
|
---|
90 |
|
---|
91 | = White page or Page Not Found (404) when clicking on a translation flag =
|
---|
92 |
|
---|
93 | This could be due to a change of the permalinks structure of your blog, to a conflict with another plugin or to a custom
|
---|
94 | .htaccess file which doesn't permit Global Translator to add its custom permalink rules. Try to refresh the Global Translator
|
---|
95 | rewrite rules just pressing the "Update Options" button from the Global Translator admin page. If the problem persists,
|
---|
96 | try also to deactivate all the other existing plugins and check your .htaccess file and comment out all the non-standard rewrite rules.
|
---|
97 | If you discover a conflicting plugin please send me an email (davide at nothing2hide.net).
|
---|
98 |
|
---|
99 | = "Sorry, the translation engine is temporarily not available. Please try again later" message when using Google Translations engine =
|
---|
100 |
|
---|
101 | You're using an old version of the plugin. Please upgrade to 1.0 or later.
|
---|
102 |
|
---|
103 | = The translated page has a bad/broken layout =
|
---|
104 |
|
---|
105 | This is due to the translation engine action. I cannot do anything in order to prevent this problem :-)
|
---|
106 | I suggest you to try all the translation engines in order to choose the best one for your blog layout
|
---|
107 |
|
---|
108 | = I've just changed my permalinks structure or just upgraded Wordpress to a newer version and Global Translator doesn't translate anymore =
|
---|
109 |
|
---|
110 | Everytime the permalinks structure of your blog changes, the custom rules previously added by Global Translator are overriden.
|
---|
111 | To solve the problem you must just refresh the Global Translator Options ("Update Options" button) on the administrative area.
|
---|
112 |
|
---|
113 | = I've removed one or more available translations but the search engines continue to try to index the corresponding urls =
|
---|
114 |
|
---|
115 | When you remove one or more translations, the plugin will begin to return a 404 Not Found for all the corresponding translated pages.
|
---|
116 | In order to notify a search engine that one or more urls are not available anymore you should add a deny rule on your robots.txt file.
|
---|
117 | For example if you decide to remove the German translation you should modify your robots.txt as follows:
|
---|
118 | User-agent: *
|
---|
119 | [....]
|
---|
120 | Disallow: /de/*
|
---|
121 |
|
---|
122 | = How can I discover if my blog is currently banned by the translation engine? =
|
---|
123 |
|
---|
124 | Go to the Global Translator admin page. If your blog has been temporarily banned, a warning message will appear inside the "Translation engine connection" section.
|
---|