Building up a Wiki – Help Appreciated

Just announcing that we are building up a manual/wiki site for oTranCe.
https://mysqldumper.jira.com/wiki/display/OTC/Home

Of course, this page will be linked from http://www.otrance.org once there are a couple of entries. Here is a good example of how it could look like in the near future:
https://mysqldumper.jira.com/wiki/display/OTC/Updating+from+SVN+source

BTW: kudos to Daniel who made this script – it is already in use on oTranCe demo installation and on OXIDforge translation center

If you want to join this project and help us writing the documentation, please feel free to drop us a note. We appreciate your help!

oTranCe Demo Available

Touching something is better than to watch it, isn’t it? 🙂

That’s why, a couple of days before, we set up a demo installation of oTranCe. Basically, you can check the functionality of the translation platform without any restrictions here.

You will get unlimited admin access with the user name “admin” and the password “admin”. Don’t worry – you can’t damage anything – not even with an import of your own language files: none of the hold data in the system will be used; the demo installation will be reset ever day. Those of you who want to see how an interpreter will look at oTranCe shall use “tester” as user name and “tester” as the appropriate password.

Good luck with checking the system now! Let us know what you like, if you could determine bugs and what doesn’t work properly in your opinion yet.

Performance Improvements Before oTranCe Version 1.0

While the first interpreters where busy filling the language databases we recognized that the performance gets pure on the “Entries”-page at a certain amount of languages and/or keys.

The oTranCe team reacted immediately and already could find a solution for this behavior.

Before, the search mechanism took effect in both, language keys and translations. Additionally, a filter was applied for languages, assigned templates and for not yet translated phrases. Thus, the generated SQL query became too complex and brought the MySQL server to its knees. Putting out the search results, an additional query was generated per output line to pick up all related information.

To avert this performance issues, oTranCe now became more intelligent. The single different queries have been capsuled so that every single area can care about its specific requirements. Moreover, the additional output data will be picked up in a single step and thus will keep the load of the MySQL server on a lower level.

At the end of the day, a much higher speed of replies has been reached. Interpreters don’t have to wait too long for the reaction of the surface and can work much faster.

You can download the changes with a new SVN checkout.

Print Article About oTranCe at PHP Magazin

article about oTranCe at PHP MagazinHello and welcome to our brand-new project website where you can find all information about oTranCe – the webbased translation platform for your multilingual web project. Please let us know if you are missing important information. From now on, we will publish all news about oTranCe on this blog. Make sure you register to the oTranCe RSS feed.

We are proud to announce that an article about oTranCe has been published in German in the latest PHP magazin which was published on November 9th. This article describes how to manage translations of your project with oTranCe.

Of course, we cannot copy the entire text to this blogpost due to possible copyright violations. If you feel fancy, you can order this edition of PHP Magazin.