In one of the previous tutorials we have discussed how to introduce support for I18n into Rails apps. Today we will continue covering back-end frameworks and talk about localization of Phoenix applications with the help of Gettext. You might not have heard about Phoenix before, so let me say a couple of words about it. This is a server-side MVC framework written in Elixir, which is a functional programming language working on Erlang virtual machine. The framework itself is quite young but still it is very promising thanks to the Erlang’s and Elixir’s features. It is very fast, scalable, and concurrency-oriented which is really important for heavy loaded applications.
In this article you are going to learn how to translate your Rails application into multiple languages, work with translations, localize datetime, and switch locales. We are going to see all these aspects in action by creating a sample application and enhancing it step by step. By the end of the article you will have all the necessary knowledge to start implementing these concepts in real projects.
In the localization of any software including websites and web apps, mobile apps, games, IoT and standalone software, there is no continuous, logical document similar to articles and books. Instead, there are hundreds or thousands of words/phrases which by default do not carry implicit context and quite often are simply impossible to translate without knowing some background information. For example, take English words like go, pool, mine, draft — depending on the situation, they have completely different meaning. This is one of the many reasons why a modern product team should consider using a professional translation management system (TMS) instead of translating localization files straightaway or even worse sending Microsoft Excel/Google Docs sheets to translators.
You may be writing your first Android app or you may already have a few. Why are you writing them? Hopefully, you want your apps to grow and be used worldwide. But most of the world does not speak English. Sooner or later, you will need to support multiple languages. In this article we will explain how to get started with Android localization using step by step examples.
Can you manage your iOS app’s metadata in iTunes Connect? It’s trickier than you think.
Metadata are sections about your app: name, description and what’s new.
At first, managing metadata is easy: you update one text file and copy its contents into iTunes. But time goes by and your app grows. You support more markets and localize into more languages. You now have 10, 20, 30 files, often full of characters that you can’t even read. Updating them all like you used to becomes a hassle. Repeat this with a couple more apps, and it becomes a nightmare.
Every global app reaches a point when it takes too much time to update its description and what’s new sections manually. The more metadata you manage, the more time it takes.
“How do I integrate Lokalise into my deployment process?” All your answers are here, in one place. Bookmark this page for handy links to the latest list of Lokalise integration tools.
The process of localization is sometimes tedious and unorganized. Lokalise helps you solve this problem. In this tutorial, we’ll focus on enabling localization in your application, adding, managing and integrating localizations in your project.
This tutorial is based on Xcode 8.2.1, it shows how to setup localization from zero to hero and use Lokalise as the translation management platform. If you are a seasoned localization master, we’d still recommend going through and take notes of some specific localization details.
That’s a common situation when you are developing your app for two and more platforms – say, iOS and Android, and some key names and values are the same and some are different. Lokalise can help you to avoid double translation work and stay clean in general by automatically merging these keys.