FAQ

There are currently three colors used

• Red – no translation was done
• Yellow – translation was done by a robot
• Green – translation was done by human (or approved by one)

You can wrap the text with an HTML class of “no_translate“, for example:
<span class="no_translate"> This text is not translated </span>

You may also use the following shortcode when appropriate:
[tp no_translate="y"] This text is also not translated [/tp]

The code HTML tag will also prevent translation:
<code> $this_code_won't_be_translated </code>

Using the wordpress editing, add a custom field called tp_language and insert the two letter code of the language used in that post, so if your blog is in English and you have a post in Spanish just add tp_language es as a custom field.
Update: more recent versions of the plugin simply allow you to set the post language with a select box that appears below the post

Yes, with the appropriate shortcodes you can make it work. Here is a small example for English being translated to Spanish.

Wrap the current text with the code:

[tp not_in="es"]Hello, World[/tp]

Add the new text at the bottom wrapped in the following code:

[tp lang="es" only="y"]Hola, Mundo[/tp]

Yes, although a bit tricky – you can either use the $my_transposh_plugin->target_language as part of the image descriptor, this will load different images based on the current language. Alternatively, in places where shortcodes are supported you can use the mylang shortcode as in the following example:

<img src="http://s.transposh.net/s/logo[tp mylang="y" lang="he,es"][/tp].png" title="transposh logo" width="300" height="86" />

If the same text appears somewhere else on your page, you will be able to translate it there. Otherwise you will probably find a bunch of semi transparent translation icons at the end of your HTML (not necessarily the end of the page). You can also find those by clicking on any item and then using the next/prev buttons all the way to the end.

You must make sure that you have enabled the “translate in default language” option, otherwise the parser will not process the page and hence won’t hide that text.

The option is not meant for translating from your default language to the same language (just edit your posts!). It is meant for translating elements that were written in other languages on your default language pages. A good example of this will be comments that were posted in your non-default language and will get translated. This also might be useful in cases where you have some text in another language which you don’t want or need to translate, if that’s the case just make sure it is wrapped with a proper lang attribute such as <span lang=”fr”>(your French text)…</span>

Three background colors are used

• Green – this language is active and all users will see it
• Yellow – only users with translation capability can see this language (this is disabled once anonymous translation is available)
• Blank – language won’t appear on widgets

You may drag and drop the languages in order to set the order in which they appear in the widget. You can use the sorting links below to sort the languages and put the default language first. Dragging is also used to select the default language.

Wiki has proven itself quite a valid model on the Internet. More people have good intentions than bad intentions and that can be harnessed to get your message out to more people. Future versions will give more focus on preventing spammers from defacing sites.

By default, automatic translation is on and it should be kicking in. If its off, and you don’t have enough privileges to translate, nothing will happen.

Please be reminded of the following “rules of thumb”

1. A language marked as viewable will have its flag shown inside the widget.
2. A language marked for editing will allow a translator (anyone marked in the ‘who can translate’ section) to manually edit the page. i.e. the translate check-box will appear in the widget.
3. Enabling automatic translation will automatically translate a page (without requiring entering edit mode) for anyone viewing the page regardless of the their role. However it will only take place for languages marked as editable.

Also – please take extra care to validate your html, adding extra tags that are unclosed in the template may lead to our parser breaking. Use the w3c validator service for more details. If everything is set up correctly and still nothing happens, please contact us.

The plugin works on one theme yet seems to fail on another. This might be caused by themes which don’t include the wp_head and/or wp_foot functions so the transposh.js file is not being included, try to include it manually by modifying your theme.

This feature is still under development. Until the feature is integrated into the plugin, you’ll have to recover your key from us, just leave a comment on this page and we’ll provide you with the required information.

Yes, MISolutionz.com provides hosting service and have been using transposh themselves, if your current provider is touting the “high cpu” mantra, you may consider switching.

Make sure you have upgraded to the full version, instructions are in this post:
Version 0.9.3 – Where did my flags go?

You can edit the constants.php and add a line to the languages array, or just contact us to add your language

In the languages array in the constants.php file change the two letter ISO code used for that flag

For example, to change the flag for the English language from the stars and stripes to the Union jack find the following line

'en' => 'English,English,us,en_US',

And change it to:

'en' => 'English,English,gb,en_US',

Note that this works out of the box only in the non css version of the widget, to make this work in the css version you will have to modify the image used.

Just add the following line to your template:
<?php if(function_exists("transposh_widget")) { transposh_widget(); }?>

If you want to use a widget style other than the default style and title, you can use something like:
<?php if(function_exists("transposh_widget")) { transposh_widget(array(), array('title' => 'Translation', 'widget_file' => 'flags/tpw_flags.php')); }?>

The widget file is actually the location of the widget source file in the widgets sub directory, you can see all the possible options in our development site. Some intereting options include 'flags/tpw_flags_css.php' and 'select2/tpw_select2.php'. You may also check all the current options in our widget gallery.

If you want to make sure that the external .js and .css are being included, please make sure to add the ext_call param like:
<?php if(function_exists("transposh_widget")) { transposh_widget(array(), array('title' => 'Translation', 'widget_file' => 'flags/tpw_flags.php'),true); }?>

I want to obtain the current language setting in my code/theme

Since version 0.8.4 you may use the following global function:
transposh_get_current_language();

This is on our todo list.

Please make sure you are using PHP5 and up. PHP4 is not supported

This error is mostly caused by a low php memory limit settings. Try increasing your php memory limit.

A lot of effort has gone into the optimization of our plugin, however, there are some actions that you might need to take

• We strongly recommend using a local memory caching plugin, such as APC. Using this php extension will dramatically reduce the load on your mysql server.
• We also recommend installing a wordpress caching plugin such as WP-Super-Cache

If you can’t do any of this, a better hosting service is recommended, we don’t link to any here because nobody has offered us any payment yet 😉

Another .css file might intervene with ours in a way we didn’t predict yet. Either fix that .css on your own or contact us.

First, you can always use another option for the plugin which is more compatible, such as the selection box. Furthermore, you can change the .css from transparent background to your page background color. And last – we urge anyone still using IE6 to upgrade…

Cufon and Transposh are not really fond of each other. Our best suggestion is either to remove cufon (and delete automatically generated translations) or at the least disable it on translated pages. Mind the fact that on some languages cufon will cause no characters to be displayed at all.

First, the feature is marked experimental for a reason 😉 , but the reason this might happen is because two strings in your default language gets resolved to the same string. An example in English will be words such as Hello and Hi which might get resolved to the same word in a different language.

Fixing that error can be done by either disabling the feature, or working on the database directly to eliminate the duplication. In the future we will fix the back URL resolution to become more predictable.

(http://aciddrop.com/php-speedy/)
Users of php speedy will have to deactivate it, add “transposh.js” in the ignore list, click on “Test configuration” then reactivate it.

Currently the plugin is able to add the multilingual urls to the sitemap, and you need to add the following line at the sitemap-core.php, add-url function (line 1509 at version 3.2.2 right after the AddElement)
do_action('sm_addurl', $page);
We hope that future versions will include this by default, and for now you can get the patched file from our site.
After a change of languages used, you are welcomed to trigger a new sitemap buildup.

Update 27/3/12: Please note that version 4 beta supports Transposh by default, no need to do anything.

The support for wp-super-cache includes the invalidation of cached pages after a translation is made, which should reduce the issue with incorrect pages being displayed and redundant calls to the machine translation agent. After a change in the widget layout or the language list you are still expected to invalidate your cache.

There are a few things that you need to verify if no translation is happening when you visit a translated URL:

• Check that the transposh.js is being included in your html
• Check that there is no old version of jQuery.js being included by your theme
• Check your browser’s javascript console for any errors
• Try fixing the database in Transposh’s settings
• Try to disable the progress bar (might help if there is a jQueryUI conflict)
• Try using the translate all button in the settings page

There are a few things that you need to verify if no translation seems to stop in the middle:

• Check that your html passes w3c verification
• Make sure no hidden characters sneaked in (such as UTF+0003), this sometimes happens when pasting from word

This is most likely caused by a jQueryUI conflict, please check that no other version of jQueryUI is included by your theme or another plugin,
You may also try to use the jQueryUI override advanced parameter (1.8.24 is a good number)

The correct place for that would be our development site