Agile software development is de facto standard for today’s software management (at least for web and mobile software). No matter which methodology you are using, a fast feedback loop and continuous releases are big factors for successful products. However, this faster environment introduces new challenges for software development, such as testing, deploying and translating. While testing and deploying are mostly solved thanks to great libraries (e.g. JUnit) or services (e.g. Codeship), translating is still a painful and manual task for many software companies. My guess is because it involves new stakeholders (translators). Hence, a much more complete view must be applied. The problems of translators are very much different from those developer encounter. In this article I will discuss current technologies for localization (i18n) and how they help or hurt a hassle-free software translation workflow.
Our internationalization plattform Lingohub started as a side project developed solely with Ruby on Rails. I had troubles at that time translating the software I was working on. It became pretty clear that my vision of such a platform goes far more beyond what I could achieve as a side project. I teamed up with Markus Merzinger (@maerzbow) and Lingohub was born. Markus and I are both seasoned Java Programmers, we together have 20+ years experience working on small and really large Java programs. We both weren’t Ruby/Rails experts when we started Lingohub, but after working 2,5 years solely with Ruby/Rails I would say our Ruby skills are pretty solid. Nevertheless, we decided to move our entire code base from Ruby Rails to Java/Spring and I want to share with what drove us to do this (drastic) step.
lets talk about key features of Rails 3.1.0
1. Asset Pipelining
The two important folders of Ruby on Rails code structure are
- app/ * ———– contains technical code
2. Generating Sprites Another feature introduced with Rails 3.1 is about Sprite Generation which is basically a method for combining many graphics into a single image. That single image will be then displayed using CSS.
<% sprite_css(“icons”) %> this code
- Combines all images of a folder
- Generates CSS
Ooh ! How can we forget what people tweets about Rails 3.1 ? I guess this is a cool tweet.
Amazing !!! Isn’t it ??