Well ahead of the deadline posed by Google Translate API to stop working, we were finally able to compile this new release. This one followed a long period of problems that were presented by the older version, mainly because of the fact that Google decided to pose limitations on usage before their deadline which caused the previous versions support requests to surge to new heights. The Google change also triggered an API limit in the Bing translation API, since users were switching engines, which overloaded the Transposh hard coded API key for Bing.
At this point we had a solid version, which seemed like a good thing to release, but no, we had to have some other features in, so we finally decided to tackle the issue of multiple widgets support (and title selection too, yippee!). Seems quite straight forward? but no, this caused a major rewrite of our widget infrastructure as well. Actually improving it quite drastically with changing the way css was added, and the way the widgets notified the servers of change in language (we now avoid a useless POST call to the server). While writing that we were lucky enough to stumble upon a PHP5.3 to PHP5.2 incompatibility issue with a set of other problems which held our release back another week. We want to thank the many users that have put up with our beta releases and helped us find problems that were hidden under layers of code and complexity.
We also took this opportunity to change our terms slightly, if you are displaying Google ads from AdSense on your translated pages, we will take 1/1000 of that space for use with our own adsense code, so if Transposh is helping you generate a revenue of $10K you will be buying us coffee! So thanks! To clarify things a bit, we don’t create additional ad space on your page, and we won’t insert any ads or change your layout, if you have no ads, we do nothing. If you think that this is asking too much, you may simply delete our plugin, whistle a soft tune, and be on your way. If you want a commercial license, we don’t sell them yet, but they’ll probably cost more.
Other changes to this version include:
- Added Catalan and Hindi support for Bing – speaks for itself.
- Dropdown widget improved css – it actually looks much better now.
- Support for Memcached – if APC and other opcode caches were too much for you, now you may use memcached and have a lot of fun.
- Better 404 page handling (don’t create new links to non-existing pages) – meaning the google crawler will hassle your site less.
- Fix caching on rackspace cloudsites – they had x-cache installed for opcode cache, but with no user memory, which caused a surge in logfiles – now fixed.
- Many more minor fixes – We might count those, but we don’t have enough fingers.
- Turkish Translation by Semih Yeşilyurt.
We hope you’ll enjoy this version, and as always, waiting for your comments, ideas, suggestions and flames.
P.S – Tested on WordPress 3.3 beta4, works great.
We are happy to present you all with our newest wordpress plugin release. This is a rolling release that does not include any major changes or something that is too groundbreaking. So we’ll just walk over the changelog and explain the news.
- We have imported some improvements to the simple html dom which serves as the base to our parser from a new upstream release, not much news here
- Allow setting of a post/page language with a simple select box. This is not a new feature, as this could have been handled in the past my adding the tp_language meta to the posts manually, however it does simplify the process, and it also make sure that translate default language is turned on so that the feature will actually work.
- Warn about some conditions that we can’t fix and a user should probably be aware of. Currently there are two condition we notify about, which are the ones that made most of our support questions to date. First we warn about low memory conditions, and we urge people to increase their php memory limit (or switch to a decent hosting service). The second warning is about the lack of APC or similar which can improve the performance dramatically (again, switch to better hosting!). The warnings can be safely removed by pressing the small X symbol and the side which will assure that you won’t see those warnings in the near future.
- Allow collecting of anonymized statisics upon user consent. Please please allow us to gather some data! we really want some vanity statistics like we are running on 1 zillion sites and are translating a gazillion pages per second!
- Fixed some minor warning notices reported by users. No longer will your logs be clogged after removing our ads!
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 Translate - Bengali, 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.
We hope you’ll enjoy this version.
This release comes in a bit late on our schedule. But it already broke our single day download record by crossing the 500 mark.
This release although small in nature does have some nice additions.
First, the default language set in Transposh now overrides the one that is set in the WP_LANG constant, this allows a WordPress MU installation in which every site can be managed in a different language on the backend. A feature which I enjoyed by finally allowing my kid to have his own personal blog in a language he can manage.
We have added a tp shortcode that enables to output the current transposh language, although it might not sound like much, this small additions allows displaying different images for different languages, you can read about it here.
An addition of a few constants in our parser code, now allow coders (not users) to change our parser behavior to break phrases on larger chunks, see the top of our parser.php for documentation.
More changes and bug crashing include:
- Iframes included inside pages will now attempt to include proper language
- Fixed bug with using the only=”y” parameter of the tp shortcode which made incorrect detections of source language further in parsing
- Added German translation by Jenny Beelens from professionaltranslation.com
Enjoy this version, tell your friends about it, don’t tell your enemies anything, consult with your lawyers if you really want to and don’t forget the importance of your family.
PS: We know about the scheduled Google Translate API deprecation and the plugin will still work, details will be uncovered in future versions.
Today we have released version 0.7.3 which adds support for shortcodes inside wordpress posts, this can be used to do some neat stuff and for which we have created the video above, so if you have five minutes free and nothing better to do, just watch the video. Otherwise we would recommand reading the documentation at http://trac.transposh.org/wiki/ShortCodes.
Some more bug fixes were added to this release, mainly reducing the load (and duplications) that bots might create on edit pages, and eliminate unneeded session files for bots.
Enjoy this version!
We have just released version 0.7.2 with a few bug fixes and three added translations to the plugin.
- Italian translation by Marco Rossi
- Persian translation by Sushyant Zavarzadeh
- Spanish translation by Angel Torregrosa
Two years (and a day) have passed since version 0.0.1 was released and one year since version 0.4.3 was released. In this year we had over 32,000 downloads in comparison to 13,000 in the year before, and we have more features and a bit more grown up product.
We wanted to celebrate this day with the release of the proxy service, but unfortunately this will be delayed a bit, however – the dedicated 24GB ram server is finally up (hosting this site) and we will soon be ready to rumble. Looking forward to your ideas, suggestions, kind words and anything you might want to throw at us.
Work on transposh is commencing at full speed, and when a new version is reaching a stable state we attempt to release it to the masses for general consumption. This minor version does not bring any new major features but it does go to fix some points that needed attention.
So without further ado, lets review the changes:
- Two language translations to the plugin were added, Dutch with the help of Roland Nieuwendijk and Russian with the help of Romans Matusevics. If you want to help, just contact us and get our eternal gratitude (and credits)
- Marking of excerpts were fixed for tp_language posts
- Dramatically reduce number of database queries on translatable urls (from thousands to one)
- Fix for automatic translation when anonymous translation is not supported on non google engines
- Fix buddypress (and hopefully other) redirections on single activities pages and other double redirected pages
- Fix for regression with after post translation and translate all
We hope you’ll enjoy this version, and we are waiting for your comments and feedback.
The next major version release of Transposh is here, and to celebrate the occasion we have created a short video (about 11 minutes) . Introducing the new features available in the new version. You are more than welcomed to watch the video and nominate it to the next academy award prize for translation plugin update movies.
The first thing you will notice in the newer version is the major update to the user interface, we have added a couple of highly requested features to the interface such as next/previous buttons, approval of automated translations and finding phrases that are translated. Another interesting feature that we added is the ability for a translator to see the original phrase in a different language if it was already translated to said language manually, so assuming you have a Hebrew blog which you translated to English, a translator may be able to translate your site from English to another language, which might be easier for him. I want to thank Hanan for originally asking for this feature. It is also possible now to remove translations from the history dialog, which is a step in the direction of working on stricter control on translation quality.
The interface is also sleeker, with nicer ui that is also localizable and themable, you can set the theme in the widget settings, and a good place to get a grip on how it will look is themeroller. If you want to help us by translating the interface to your language and getting the credits for it, please let us know by using the contact us option above.
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.
We would like to thank Joshua Hansen and Scott Caveza for their help in identifying and helping us debug two XSS vulnerabilities that had the potential to effect users using internet explorer browser with versions lower than 8, or when xss protection was explicitly off. We avoided the urge to call this version 0.6.6.6 and resumed the regular naming policies. Those vulnerabilities don’t pose any risk to webmasters or hosters using Transposh, but to users that might trust scripts from these sites by using the sneaky XSS method.
This release also bundles two other changes that were already committed and would have probably waited for a later release otherwise, the first being a small improvement to the parser, enabling support for some more html “breaker entities” such as ’ which were created by software trying to outsmart the user, we would like to thank archon810 on his help in this bug report.
Last but not least is a change in the support for Google Sitemaps XML generator, the patch has one letter removed in order to have proper support for php5.3, and on other good news, the coming version 4 of this plugin has support already built in, this version also helps in breaking the 50k url limits that some users had. So we would to thank Arne Brachhold on his great work on this project.
So everybody, go and upgrade! just because finding an image to match this post was such a difficult fit.