Version 0.6.7 – What’s next?

Image by

What's next for Transposh?

Yesterday we have released version 0.6.7. This version includes a few minor fixes, both for the ability to translate more phrases when google does not detect the source language correctly, and for the ability to include direct links to static files (those will cause a 301 redirect to occur).

However what is more important is that we have finally been able to cleanup our milestones, and set the gears in full motion for the next major version of Transposh – which will be 0.7. The focus of this version will be a major improvement to the translator frontend interface, and we have put the requirements for this online in our development site at Everyone that wants to influence the next version is welcomed to edit and comment on that wiki page or create a ticket for us. We will review each request and try to fit it into the schedule.

On some other news, we would like to thank Colnect, our new sponsor for contributing a new vps for Transposh which will hopefully make the site go a bit faster. We have also attempted to use cloudflare to improve our service, however we are having mixed results with that, so if you are having any problems accessing this site, please let us know.

Last on the agenda, an alpha version of our plugin for blogger is on the works, if you have a site on blogger and want to add translation to it, just contact us.

, , , , , , ,

  1. #1 by Vito on December 19, 2010 - 6:49 am

    Do you know when the url translation will be available ? I love the product but my concern is the duplicate content by google .

    • #2 by ofer on December 19, 2010 - 8:34 am


      You can see when every feature is planned here:

      If you don’t see said feature, feel free to create a ticket which will be assigned, be as detailed as possible


  2. #3 by Timo on December 20, 2010 - 12:39 pm

    When is it possible to translate from other languages into the default?

    • #4 by ofer on December 20, 2010 - 12:43 pm

      Always, when that part is wrapped in a lang=”xx” tag

      • #5 by Timo on December 20, 2010 - 2:37 pm

        It does not work for my website. ?lang = en is the default language. In other languages, words and sentences can not be translated into the default. Also, it does not work well on this page. Site uses the abbreviations of languages /en/ and others.

  3. #7 by Janar on December 28, 2010 - 12:09 am


    When I enable default language translation then nothing happens when I check the checkbox for translation. Does that work ?

    Thanks !

    • #8 by ofer on December 28, 2010 - 12:25 am

      Hello Janar,

      Translation of the default language only works where there are html elements marked with a different language than the default one, what is the point in translating English to English? However – if a user leaves a comment in Spanish, it is marked as such, and when enable default language translation is enabled it will enable the translation of said comment to English.

      I hope this clears this issue a bit

      • #9 by Janar on December 28, 2010 - 11:34 am

        Thanks for answering.

        I’m running website in Estonian and added wp-o-matic that does automatic content from RSS feed. These posts that it adds are in English. So now I have duplicate content as both the default and EN languages are the same.

        I wanted to translate the default language from English to Estonian so I will don’t have problems with duplicate content. Maybe you have ideas how not to let google crawl posts that are not /en/ in certain categories ?

        Thank you. I love the plugin.

        • #10 by ofer on December 28, 2010 - 1:12 pm

          Hello Janar,

          You can add a meta key “tp_language” and set its value to “en” this should solve your problems

          Good luck

  4. #11 by Janar on December 28, 2010 - 5:17 pm

    ofer :
    Hello Janar,
    You can add a meta key “tp_language” and set its value to “en” this should solve your problems
    Good luck

    Thanks. It solved duplicate content issue. But the translation that Google gives just doesn’t go with the quality I want to provide.
    Now I’m wondering if I can display these posts for only /en/ language ?

    Another solution would be to translate them by hand but is there an option to translate it into default language at once and not by phrases ?

    Thanks !

  5. #12 by Janar on December 28, 2010 - 5:49 pm

    I wanted to report back that I might have found a solution. Using Redirection plugin I can redirect my default language post that is in english to /en/ version of it.

    If you have any thought why it could might now be advisable on SEO side then please let me know.

    About translation I would still ask that if it’s possible to translate the whole article at once without doing it by phrases ?

    Thanks! And great work !

    • #13 by ofer on December 29, 2010 - 12:08 am

      Hello Janar,

      Any solution you choose that works for you is great, you might want to share with others what you did and why, and I’ll be happy to make a guest post in here.

      Regarding full article translation, I have eased the working with phrases issue to be soon released at 0.7 (see the basics working here), the working full paragraph thing is tricky, and might lead to defacements, however – you may change the breaking code in parser.php to suit your needs.

  6. #14 by Janar on December 29, 2010 - 9:41 am

    To get rid of my duplicated content problem when inserting a post in my second language I used Redirection plugin. I redirected the urls with default language to

    I just noticed that I have RSS links with default language code. Feed displays urls with et tag: et/date/title. I have disabled default language translation. Do you know if this is normal ?

    I see. It could be tricky as I know that Google is doing translation by phrases on it’s own.

    Thanks ! Sorry for all those questions :)

  7. #15 by Janar on December 30, 2010 - 11:24 am

    RSS works fine now.

    I changed parser.php to give more chars to be translated.

    Changed the beginnin of line 272 to return (strpos(‘?{}!|;’ . TP_GTXT_BRK

    and before that added 600 to $char variables. It seems to work fine, although my previous translations were deleted. I see why it’s not that easy now. People don’t want to lose their translated content..

  8. #16 by Ahmed on January 6, 2011 - 3:57 am

    there is a feature I wish you can provide soon. in wordpress admin panel when I attempt to click on the button translate all it start to translate posts everytime from the start (it insist on checking all posts from newer to older) this process take long time searching for untranslated posts.
    if you could make the script store the position of the translate all attempt if the same setting doesn’t changed, that would be much easier and faster

    • #17 by ofer on January 6, 2011 - 12:59 pm


      When a post is translated, it will take much less time to pass it in the translate all, which is not intended for every day use, the resume you suggest will be a little tricky to implement although possible,

      If you want this to happen, the trac site is your friend at

  9. #18 by Tamino on January 8, 2011 - 4:08 am

    My english is not so good…

    I have installed transposh in WP 3.04 and receive the following announcement:

    Fatally error: Out of memory (allocated 32243712) (tried to allocate 77,824 bytes) in/homepages/39/d247477599/htdocs/wordpress/wp includes/class simplepie.php on line 14908

    What now?

    • #19 by ofer on January 8, 2011 - 3:14 pm


      You need to increase your php memory limit.

      Good luck

      • #20 by Tamino on January 8, 2011 - 7:45 pm

        Thanks for info, but unfortunately my provider can not be :the(. I found a solution. All “large” Plugin disable, Transposh install and configure. Then select all.
        SUPER TOOL !

        Thanks for the quick help.

  10. #21 by Ondrej on January 12, 2011 - 2:17 am


    It looks like Esperanto displays the USA flag in the widget. Have a look:

    There are two US flags. One in the upper left corner, correctly indicating English. And another, in the lower right corner, which displays Esperanto on mouse over.


    • #22 by ofer on January 12, 2011 - 3:23 am


      The w3tc css minifier didn’t take in the new css, so make sure it clears its css cache and everything will work with regards to the flag)

      Good luck

      • #23 by Ondrej on January 12, 2011 - 12:12 pm

        You’re great! Thank you!


(will not be published)