Altagram: on all platforms and in all formats

Localization Engineering

Looking for technical support for your game localization project?
Rest easy! We've got you covered!

Professionalism is an extremely important quality in this industry and it's something we at Altagram value highly. With video games being our speciality, we understand that optimized content management is complex and demands experience. We can work with any text format and from any source, thanks to our highly trained project managers, coordinators, and in-house localization engineers who can adapt to any of your requests. Upon receiving your files, we integrate them into memoQ and proceed with the localization process. Once they're complete and ready for delivery, we take care to ensure that they're returned to you completed in the format of your choice. If your preferred format isn’t on the following list, please don’t hesitate to contact us. We'll no doubt be able to handle your request regardless of format.


The most common file format for exchanging localization content. Easy to read and organize, supports most languages, and allows you to give each line that is to be translated an ID for context. Linguists can therefore translate content with maximum creativity and accuracy.
Tables that offer the same benefits as an Excel file. Be careful to check the encoding of the text when submitting.
Rarely used for in-game text, but common standards for marketing content. Naturally, free equivalents like .odt or .ods files are also accepted.
Less common than other formats, but often used in localization-specific tools.
More and more games, especially on the mobile market, are organizing their strings in this format. Our tools support them easily and without conversion.
Another common format for organizing localization data, containing a slightly different structure from the classic string file.
When translating text, staying aware of the underlying source file structure is very important. This ensures the linguists have all the information needed to produce a contemporary sounding and catchy localization. Our tools support these formats.
This is by no means an exhaustive list. Altagram also works with the following formats:

.yml, .yaml (YAML), .ini (configuration file), .js (RequireJS/i18n), .json (i18next multilingual), .json (i18next single language), .plist (Apple property List en XML), .l10n (Java l10n), .lang (Java lang), .properties (Java Properties), .md (markdown), .tmx (Translation Memory eXchange), .qph (Qt Phrase Book), .locale (Play Framework Properties), .indd (InDesign), Mozilla RDF.