Version 0.7.5 – Motalika tsiku ++

by voobie
Kuthandiza 5 kwambiri Indic m'zinenero

Tsiku chilimwe wakhala mwalamulo wayamba kumpoto kwa dziko lapansi, timanyadira kuti azipereka Baibulo 0.7.5 yathu pulogalamu yowonjezera. Izi Baibulo anawonjezera kuthandiza a chinenero amene kulengezedwa anathandiza lero ndi Google Translate – Chibengali, Chigujarati, Chikannada, Tamil ndi Chitelugu.

Pamaso mkokomo kuwonjezera zinenero anu blog, chonde kukumbutsidwa kuti zinenero ntchito ajax lochitira voti kuti ntchito molondola, chimene chikutanthauza kuti kulenga katundu wanu seva pa poyambapo ndi latsopano chingwe (kukakamiza kuti akatenge yomasulira ku Google). Choncho wanu kusankha, koma munayesedwa analidziwitsa…

Komanso izi Baibulo anawonjezera gawo kuti kuyanjana kwa mfundo kusakhulupirika malo ndi Transposh za kusakhulupirika chinenero, izi khalidwe (watsopano pa 0.7.4) analola MU owerenga kuti boma masamba m'chinenero chawo, koma Komano okwiya owerenga kuti ankafuna kugwiritsa ntchito malowo mu chinenero china kuposa kusakhulupirika, kotero tsopano ili ndi configurable.

Tapezanso bwino kumasulira UI, lotsatira ndi kale mabatani tsopano kupulumutsa kusintha wachita, ndi kukambirana sadzakhala timawerenga zokha pa kuwonekera awa mabatani.

Tikukhulupirira inu amakonda Baibulo.



  1. limanena

    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!

    • limanena

      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

      • limanena

        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 asbeta” kapena “experimental”, ndi zina. – 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, koma “keep it simpleis one of my hot buttons. Sorry you hit it! 😉

    • limanena


      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

      Zabwino zonse

  2. Little Red Frog limanena

    Muno kumeneko,

    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?


    • limanena

      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

      Zabwino zonse

  3. Jonas limanena

    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. Komabe, 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.

    Zikomo kwambiri!

    • limanena

      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, mulimonse – you just got a reply here, gzip issue, probably with a problematic setting on your site or a conflicting plugin

      Zabwino zonse

  4. Ikyo limanena

    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 limanena

    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. Komabe, from yesterday, it has appeared a blank page when i click to a specific language. So what is the problem?

    Chonde ndithandizeni! Thank all guys very much!

    • limanena


      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.

      Zabwino zonse

  6. limanena

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

Zimene Mumakonda

Anu email simudzakhalanso lofalitsidwa. Amafuna minda Chizindikiro *