Get Localization provides multiple ways to deliver your internalization (i18n) files for translation.

Upload and download them conveniently via web browser. It's easy.

Amend and automate your build process by using the API

Sync them directly from the IDE

Set an automatic import from GitHub when there is a commit.

We support natively dozens of different i18n file formats, for example iOS (.strings), Android (.xml), XLIFF, Qt (.ts), gettext (.po), PHP arrays (.php), YAML (.yml), INI, Java properties and many more. We have support also for text documents (e.g. for store descriptions) and Microsoft Office DOCX documents (e.g. for user manuals). We can also provide custom XML formats based on your needs.

Setting up the project

Starting the project takes only couple of minutes. You can push the i18n files to the system in your preferred way. Easiest way to get started is to just use the Files panel in your project and upload the files directly from the browser. If you have multiple i18n files, you can just zip them and upload the zip file.

Automate everything - create an efficient develop-translate-feedback loop

By automating we mean that you should integrate Get Localization into your build process. This helps you with your future updates, saves you from stupid questions and will keep your Get Localization project active all the time. Your changes are the fuel that keep the engine running, so make sure to push them. This helps managers to see how much content there's untranslated and will let translators know there is new content available. This has an immediate effect on how managers and translators work, as they have the information they need and they can run the project better without bothering development all the time.

Remember also to automate the download of translations, just pull them from Get Localization to the correct directories automatically. It is easy and saves you from doing manual file management each and every time you want to update the translations. This also allows you do update the translations much more often, so possible issues with them can be spotted and addressed earlier.

Communication

Translators don't always understand the context where a string is used. That is why they may have questions. Get Localization allows to comment each string, when somebody asks a question you will get an e-mail notification with the link to the correct string. Just fire your answer away and it will help all the translators who are working. Efficient communication without the hassle.

Benefits for developers

No manual file management

No cut'n'pasting from file format to another, you can e.g. Android and iPhone files in sync automatically.

No manual updates of translation files, they automatically match with master file.

No character set problems, files are always in compatible format.

No syntax errors, translators see only strings they translate. File syntax cannot be accidentally modified.

Better communication channel

Overall less hassle and more enjoyable projects