Ti ikede 0.7.5 – Gunjulo ọjọ ++

by voobie http://www.flickr.com/photos/vinish/960942349/
Support fun 5 diẹ Indic awọn ede

Ni ojo kan lẹhin ti ooru ti ifowosi bere ni ariwa ẹdẹbu oṣuṣu, a ni o wa lọpọlọpọ lati mu ti ikede 0.7.5 ti wa ohun itanna. Yi ti ikede ṣe afikun support fun titun awọn ede ti won kede bi ni atilẹyin nipasẹ loni Google sélédemírán – Ede Bengali, Gujarati, Kannada, Tamil Telugu ati.

Šaaju ki o to sare siwaju lati fi awon ti awọn ede si bulọọgi rẹ, Jọwọ ti ni leti wipe awon ti awọn ede lo ohun Ajax aṣoju ninu ibere lati ṣiṣẹ bi o ti tọ, eyi ti o tumo si wipe won o ṣẹda kan fifuye lori olupin rẹ lori akọkọ gbemigbemi pẹlu titun kan translation okun (muwon o si bu awọn translation lati Google). Nítorí ti o fẹ jẹ tirẹ, ṣugbọn ti o ba ti a ti gba iwifunni…

Siwaju siwaju sii yi ti ikede ṣe afikun awọn aṣayan ko si yi danu ni aiyipada locale pẹlu Transposh ká aiyipada ede, yi ihuwasi (titun lori 0.7.4) laaye M. awọn olumulo lati ni abojuto ojúewé ninu wọn ede, sugbon lori miiran ọwọ nbaje awọn olumulo ti o fe lati ṣakoso awọn ojúlé kan ninu ede ti o yatọ ju won aiyipada, ki bayi ni yi configurable.

A ti tun dara si awọn translation UI, nigbamii ti o si ti tẹlẹ awọn bọtini bayi fi awọn ayipada ṣe, ati awọn ibanisọrọ yoo wa ko le tun-ti dojukọ lori tite wọnyi awọn bọtini.

A lero o yoo gbadun yi ti ikede.



  1. wí pé

    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!

    • wí pé

      Hello David,

      Not everything will be configurable, as we don’t seek to overwhelm a user with too many options, tun – at 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

      • wí pé

        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 as “Beta” tabi “experimental”, ati bẹbẹ lọ. – 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, sugbon “keep it simpleis one of my hot buttons. Sorry you hit it! 😉

    • wí pé


      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

      O dara orire

  2. Little Red Frog wí pé

    Hi wa nibe,

    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?

    O ṣeun siwaju!!

    • wí pé

      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

      O dara orire

  3. Jonas wí pé

    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. Sibẹsibẹ, 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.

    O ṣeun gidigidi!

    • wí pé

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

      O dara orire

  4. Ikyo wí pé

    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 wí pé

    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? Jọwọ ran!

    Ibeere miran, I have also installed this plugin to another site, It has been good before. Sibẹsibẹ, from yesterday, it has appeared a blank page when i click to a specific language. So what is the problem?

    Jọwọ ran mi! Thank all guys very much!

    • wí pé


      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.

      O dara orire

  6. wí pé

    DARA… 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 🙁

Fi a Reply

Adirẹsi imeeli rẹ yoo ko le ṣe atejade. O beere aaye ti wa ni samisi *