It has been three years (and three days, and thirty three hours) since the first version of Transposh plugin has been aired on the wordpress.org plugin repository.
Time surely flies.
This has been the first leap year (29th February) and a real leap year for Transposh. The plugin has been downloaded from the repository over 50,000 times this year and has made a steady growth of features and total number of languages supported. And today with the addition of Hmong Daw we are the first plugin to support a total number of 66 languages.
This was a really interesting (as in, have an interesting life) year for the automatic translation industry and plugins, where Google has nearly dropped their API support (only to switch to a pay model) while Bing imposed new limits. Transposh has successfully overcame those changes, while other plugins did not survive.
What does the future holds for Transposh? We are slowly boiling some new stuff, working on our vision to improve website translation, when things will be ready – they will be out. Meanwhile, your continued support is important to us, sometimes a simple email with “your plugin is great” drives us to continue. So if you believe we are doing well, drop us a line, if you think we should improve things, drop us a note, and if you think that we suck, we fail to understand why you have read this message up to this point 😉
Wishing ourselves a great 4th year, maybe it will end with a bigger cake 🙂
long life to transposh, even if I complain, I still use it 🙂
I didn’t update yet the latest version so I will check
I do not update it now because I do not know any new function compare with old version. And could you add a function which can make every page to real .html page, this can make wordpress faster..
Thank u so much..
Updating is generally a good thing, regarding making it faster, you may consider using a cache plugin (such as wpsupercache) that will probably achieve the improvement you are looking for.
I use this plugin for long time. But our hosting told me our site overload CPU, does this plugin can cause this problems?
Thanks again..
Hi,
This plugin does consume CPU time, which can be drastically reduces when using a supported in memory caching solution, such as memcached or APC
you can ask your hosting provider about those
Good luck
Hey, said, that after the change of language changes the status of a user registered on the guest.
How can I solve this problem?
I am not sure I understand what issue you are reporting, try to provide more details so I’ll be able to help.
In WP 3.4 + Transposh 0.8.2 this problem, do not watch, maybe the reason was in WP.
Thanks.
Hello,
Great plugin, it’s cool.
But the syntax of the translation is quite unusual, is there any way to put sentence parts to another place when editing?
Greetings
Bane
Hello there,
Still working on that, however there are a few constants that may be changed at the top of the parser.php file, although this will probably won’t be supported in the future, and will probably invalidate your current translations.
Hi there ! Just corrected the French version of your post 😉 Making your website participative is a great idea, as your plugin is!
Many thanks for your great work helping us opening our linguistic borders, and Happy Birthday to Transposh!
Cheers
Alex
Oh by the way, between English and French the position of the nouns vs. adjectives is switched, and with trasposh’s way of cutting sentences quite randomly, it makes some sentences sound fuzzy with no way of reordering words properly… Is there any way to use the ponctuation to cut sentences into pieces instead of cutting them quite randomly?
Many thanks again 🙂
Alex
Hi,
Thanks for fixing the French version, highly appreciated. Care to do the same for the plugin itself?
Regarding random cutting, it is not that random, it will cut on html entities, numbers, punctuations and html. Those are rules that can be changed in the parser file, and we are working on improving the overall process. Besides the problems you mentioned there are problems related to context such as words with dual meaning and gender issues in some languages. So the answer is “still working on that”.
Thanks for the comments and input
Provide me with the files and the “how to” and I will do my best to translate the plugin.
Another problem: an image that does not appear in English version/French one. Can check on http://www.sahal.fr: ENG “About Alexandre Sahal” / FR “A propos d’Alexandre Sahal”
Hi,
First, regarding the missing image. Your theme uses something called timthumb (which I recall was a security issue at some point) and also consumes unneeded resources, I suggest you use a normal image tag and things will probably just work.
Regarding translation of the plugin, the files are already provided in what you have, the easiest way for translating the .po/.mo files as far as I see it is to use a plugin called “codestyling localization” which is quite straight forward.
We also have a small file to translate for the edit interface in the js/lang directory.
Naturally – credit is given to translators 😉
Hi I seem to be having a rather interesting problem, it looks like most languages (Afrikaans, Íslenska and more) give problems and don’t translate the menu items, and headings at all, and replace the text with nothing.. so there are just blocks with nothing in them.
Originally I thought this was caused by cufon, but once I customized it to remove cufon for all languages except my default. but its still happening.
Why would this happen?
Would using the google API key fix this issue?
Thanks for any help
Bryce
Hello Bryce,
After you removed cufon for non default language, have you cleared automatic translation database and caches for 3rd party wordpress utils?
Good luck
Looking forward to future developments and updates from Transposh. Surely it’s going to be a game changing product once complete 🙂
Hi..
This is an excellent plugin…I m grateful..
I would like to ask how could i possibly change the font the translated text appears…
For example…if i have english and greek…how could i change the greek font family (to Arial lets say – cause by default it comes up with a serif family).
Thank u…for everything…
Your plugin is great.
Thanks 😉