Posts Tagged major
On the 12/12/12 (what a lovely date) at 20:12 (an appropriate time). We have released version 0.9.0 of our plugin. This version included a major rewrite of our settings and administration page. Moving from the single very long page with oh so many options to a slick tabbed interface.
This version is not only cosmetic but it also included two major features enabled by the settings new advanced tab:
1. Inclusion of debugging support: Now we will be able to give you better support using the plugin ability to create logs, and allow remote debugging.
2. Advanced parsing rules: This feature allows you to change the way texts are being broken for translation on your site. It allows a much finer granulation and fitting the engine to your specific use case.
However – be warned, those features, although well tested are marked advanced and experimental. Use them only if you understand what you are doing.
There are so many other features and bug fixes included, that many of them deserve their own post, but for now, lets go over the change log:
* A new language selection widget based on select2 (Very nice select box with flags)
* Added ctrl keys for quick navigation of previous/next blocks (Improves speed of working with the interface)
* A new option that allows to reset the configuration file to the recommanded defaults
* Css fixes for twenty twelve theme
* Avoid loading the subwidgets in the admin pages
* Removed distinction between editable and viewable languages, now a language can only be active or disabled
* Updating jQueriUI to 1.9.2 (jQuery should now be 1.6+)
* Fixes the z-index for the old style dropdown (patch by chemaz)
* Fixes the bug with the coupling of Chinese simple and traditional
* Fix bug preventing upgrade from very old versions
* Suppress notices when widgets are created directly with our function
* Avoid rewriting urls in the default language, mainly effected canonicals
* Our script is needed when the widget allows setting of default language
* Finally solved the problem with MSN translate and CR/LF
In the days following the initial release, three bugs have been uncovered and fixed, if something simple is not working, make sure to refresh your files.
Enjoy this version!
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 http://trac.transposh.org/wiki/milestones/0.7. 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.
This version is a major release, and there is lots of new stuff in this release. so lets get over the list of items
- Now there is support for auto batch translations which makes translations faster and improves user experience, previously Transposh has to load scripts from the various auto translation backends and then it would iterate on the phrases one by one to get translations, now those are grouped together for reducing the numbers of requests made, the fact that no external scripts are loading reduces complexity and improves speed.
- MSN (bing) translator does no longer require a key, as they have upgrades their API and switched to using an application key, you can now just select the default translation engine at will, if this engine is not available for that language – Transposh will resort to using the other one.
- Transposh Google Proxy is now included to enable translation for Alpha level languages from Google (with 5 new languages supported – Armenian, Azerbaijani, Basque, Georgian and Urdu) – this proxy is located inside the plugin and redirects requests to google translate from your server allowing the script to use them. This process is slow – it increases the load on your server – and is generally not very recommended, and will be eliminated as soon as Google releases those languages to general consumption. But if you have the urgent need to translate your site to the Azeri people, at least you can do that.
- The Transposh logo and backlink can now be removed from the widget, if you choose this option – Transposh will attempt to make some money of existing ad space on your translated pages only, this money will help us in our development effort, if you don’t want to lose any money from your ads, just keep the link. The terms are readable here.
- The translate all button was also revamped, and should be much faster using batching.
The usual share of bug fixes is here, and I would like to thank Rogelio and Marko for their insightful comments and contribution to fixing those bugs. An attempt was made at the plugin header error, but as we can’t reproduce it we don’t know if it works, so crossing our fingers. If this release is badly broken for you, please report this at the comments here, create tickets for us in our trac. Bug us on our twitter account or our facebook page or by calling our cell phones, preferably at 3 am. You can always revert to the previous version, we are not offended.
We hope you’ll enjoy this version.