A short time ago we installed an own server for the continuous integration tool Jenkins. Presently the common, metric code analysis is running and checking the oTranCe Code before the release. During the next few weeks the tool will be expanded by including the automatic execution of the PHPUnit tests. Wo of you is curious and want to see if the build is green? Take a look here: http://ci.otrance.de
We want to especially thank SysEleven GmbH for gratefully allocating this server for our open source project. SysEleven is specialized in scalable high performance, especially in e-commerce. They serve medium to enterprise sized online merchants with peaks due to TV commercials, like baby-markt.de for example.
Presently, the hosting provider domainFACTORY provides a great campagne: DF wants to support an open source project of your choosing and tenders a lifelong free hosting. We applied for this package and – giddy with pleasure – came to the final round. Now we need your help: please vote in domainFACTORY’s blog for the project oTranCe! Please visit this page to the poll:
By the end of October, Atlassian announced that they retired the Source + Review bundle, bringing their hosted Subversion offering and Fisheye/Crucible OnDemand to an end by October 15th 2013. All customers and users have been requested to move their source code to other places.
Atlassian provides an easy integration of GitHub to Jira and Confluence. Also, when dealing with GitHub, we recognized that it provides a couple of other cool features that can make collaboration in an open source environment very easy and generate some additional virality called “social coding”.
Developers who want to join the project don’t have to write an email to the project owner, waiting for an answer, sending sample code, diffs etc. any longer until they get write permissions for the core repository. If you feel fancy to help, simply go to https://github.com/DSB/oTranCe, fork the project to your own account, make the changes you want to do and send a pull request back to the original repository. We will review the code and can merge it with a simple click into the main branch. Of course, your contribution will appear in the commit history with your account.
oTranCe is not a cloud-based SaaS platform nor it is bound to any hosting platform. oTranCe can just be used as a free and libre open source software, published under GPLv2 and made for building up the translator community for your software project from scratch.
Hence, oTranCe comes without any setup, license or transaction costs. It is simple to install, well documented, based on Zend Framework and easy to update nonetheless you made changes. If you need more than the importer-plugins provided already, just write your own interface (you’re welcome to contribute it ;))
import the already translated language files
use a Google API key to get translation proposals
export your project files to any SVN or to GitHub, enrich other files there and port them back to the built-in file browser. Set your project’s language files under version control to benefit from the latest translations made.
grant access to guest users (e.g. non-translators) and go viral with your project
download the present translations with a click, capable without registration
use fine grained settings for rights and roles per user
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.
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.
Hello 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.