Awa 0.7.5 – The longest day ++

by voobie
Support for 5 more Indic languages

One day after summer has officially begun in the northern hemisphere, we are proud to present version 0.7.5 of our plugin. This version adds support for the new languages that were announced as supported today by Google TranslateBengali, Gujarati, Kannada, Tamil and Telugu.

Before rushing to add those languages to your blog, please be reminded that those languages use an ajax proxy in order to work correctly, which means that they create a load on your server upon the first encounter with a new translation string (forcing it to fetch the translation from Google). So the choice is yours, but you have been notified

Further more this version adds the option not to override the default locale with Transposh’s default language, this behavior (new on 0.7.4) allowed MU users to have admin pages in their language, but on the other hand annoyed users that wanted to manage the site in a language different than their default, so now this is configurable.

We have also improved the translation UI, the next and previous buttons now save changes done, and the dialog will not be re-centered upon clicking these buttons.

Em hêvî dikin ku hûn vê Versiyon ji ê enjoy.



  1. dibêje:

    I hope that for the next release that the parser.php options will be configurable in the plugin settings so we don’t have to redo them when upgrading. Those are great options!

    • dibêje:

      Hello David,

      Not everything will be configurable, as we don’t seek to overwhelm a user with too many options, alsoat this points this keeps this feature to more advanced users which probably understand better what to expect and when to expect, and I don’t feel it is mature enough to become a part of the main core, at least not for the time being.

      thanks for the comment though

      • dibêje:

        I can appreciate that an option may not be mature enough to add to the configuration (though OFTEN one sees configuration options in software that are highlighted asbetaorexperimental”, etc. – so there IS precedentEVEN in Transposh already) As to not wanting tooverwhelmthe user, with all due respect, I don’t buy that argument in software configuration. In fact, I can’t say that I found Transposh’s options as they are 100% obvious. That doesn’t bother me. I just spend time re-reading until I understand. I know that there is a popular notion in much software that you need tokeep it simple”, but flexibility of function goes hand-in-hand with complexity. That’s a simple trade-off in technology. Translation processing is inherently complex. Better to try to manage the complexity and arrange/explain the options as best you can, than tohidethem.

        Frankly, I’m thrilled with those options and if people are involved in translation on a regular basis using Transposh the way we are, I would find them indispensable to the task and Transposh difficult to use without them. Why not open them up to more people?

        Not trying to be contentious here, butkeep it simpleis one of my hot buttons. Sorry you hit it! 😉

    • dibêje:


      I never tested this, but I guess it might work, the lack of invalidation might cause some reposting issues for translation, but try it out, your mileage will vary

      Bextê te xweş bî

  2. Little Red Frog dibêje:

    Hi there,

    I’d have 2 questions

    1) I would like to sometimes write my posts in English, and then translate them into French, and sometimes in French and THEN translate them into English. Is it possible and how?

    2) I would like to be the only one to be able to translate my posts and would like the option not to appear on the online pages. Here again, is it possible, and how?

    Thanks in advance!!

    • dibêje:

      1. You need to use the tp_language meta in your posts
      2. Just set translation permission to admin, it will appear on your online pages but not for your users

      Bextê te xweş bî

  3. Jonas dibêje:

    I have asked you many times, but did not get any replies. Even, you have removed all my comments.

    I have installed the plugin, config and add widget successfully. Lebê, when i click to a specific language, it has error:

    Content Encoding Error

    The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression.

    You can view my site, and please let me know your solution.

    Thank you very much!

    • dibêje:

      I have tried to mail you so many times, please provide a working email address in comments if you want to get answers from time to time, I would also recommend checking your spam folder content from time to time if you are waiting to anything of importance, anyhowyou just got a reply here, gzip issue, probably with a problematic setting on your site or a conflicting plugin

      Bextê te xweş bî

  4. Ikyo dibêje:

    Jonas →
    Pour ma part il s’agissait d’un souci avec le plugingzip compression”. Essaye de le désactiver pour voir si ça résout le problème

  5. Jonas dibêje:

    Thank you for Transposh and Ilyo’s replies!
    I don’t know when i enable gzip compression, maybe it’s a part of wp super cache or w3 total cache ? And now, how can I disable it? Please help!

    Another question, I have also installed this plugin to another site, It has been good before. Lebê, from yesterday, it has appeared a blank page when i click to a specific language. So what is the problem?

    Please help me! Thank all guys very much!

    • dibêje:


      Can’t really help you much with regards to the gzip, this has something to do with a conflicting configuration which we are not aware of.
      The blank pages are to be resolved by increasing the php memory limit.

      Bextê te xweş bî

  6. dibêje:

    okdamn.. with my theme (mondeofrom hawk-theme) is doesn´t work .Only the backend will be permanently translated, but in frontend it doesn´t work 🙁

Leave a Reply

E-maila te ne dê bê weşandin. qadên pêwîst in *