Changing the Source Locale of a Project
3 min. read
We recommend using English as your source language. But if you started with another language, we have a solution to change your project's source locale.
In any IT-based project, the happiness of the developing team positively impacts the whole project. For this reason, we designed and built our platform with the aim to reduce any friction in developers' localization process.
3 min. read
We recommend using English as your source language. But if you started with another language, we have a solution to change your project's source locale.
1 min. read
Complete guide to create a new library or client to sync with Translation.io
1 min. read
We have added a REST API, so that you can manage your models (segments, tags, etc.) and create custom localization workflows.
2 min. read
About half of our customers only use YAML and never use the GetText syntax, so we allow them to disable it.
2 min. read
Some Ruby gems have already been translated by the community, so why bother translating them again?
3 min. read
How to deal with Git branches when you are translating your Rails application using GetText and Translation.io
1 min. read
How to temporarily change your locale in a GetText project using Rails
4 min. read
Overview of the Rails GetText syntax regarding plurals, contexts and interpolations
3 min. read
the way translation.io deals with YAML files and the directory structure