YourOwnDB!

Hello World! Well its not the usual hello world program but some blog entries might also start with this phrase! And if in doubt, this entry is the proof! We are working on MyOwnDB that's obvious! But title says YourOwnDB? No we are not renaming it at all, rather its to convey that if it is in your own lingo, its more yours! So actually I'm talking about the localization. I'd not rephrase all about the importance of localization of software especially if its the one like MyOwnDB. When we started with MyOwnDB, it was Rails 1.2 and there was no suitable localization solution around. So in order to get the job done, we started out on our own and we wrote a plugin for us. The plugin was nice, we could localize, even it was crafted to be dual ended enabling translators to add more languages for the interface if any. But it was heavy. It had its own database to hold languages, translations and others. And this means another database have to be taken care of in deployments, releases and all the matters! When we ported the application to Rails 2.02, many good localization solutions were on the scene. After a little discussion and evaluation between me and Raphael, we agreed to pick Globalite as our choice. The transition was quite smooth. We wrote a ruby script that dumped our database containing UI translations to YAML format expected by Globalite, wrote a simple wrapper method around the Globalite translation method in order to reduce the transition cost involved and all started working fine! Next was making it possible to switch UI language from the interface, so that was also simple and we were easily able to do that. So in a nutshell, Its simple to localize MyOwnDB in your language and if you want to see it in your own language, please let us know. Well how exactly we did that, that's a matter which needs little recalling and not only that, I leave it for a separate blog entry! Regards, Mohsin Hijazee