You searched for "file formats"
WE FOUND 67 RESULTS MATCHING YOUR SEARCH
Translation Memory Fill-Ups can now occur based on context for users of XLIFF, PO, XLSX and QT file formats. A string which has multiple meanings will now be saved in Translation memory along with its context. This will help differentiate the meaning in cases where the same string is included in your project(s) more than once.
In "Translation Memory"
No need to rely on developers to fix minor typos and wording in source text by having them continuously upload source files. Such limitations cause delays in the localization process which means that tight deadlines might have failed to be met. Project maintainers can improve the wording in the source text by using the Transifex Web Editor. Customers who want to ensure proper grammar and alignment with other resources (marketing emails, Company’s Website) can now simply use the Translation editor in the same manner that they translate strings to other languages. After all the quality of the source text does matter.
In "Projects & Content"
Working with multiple branches and multiple developers can be tricky. This guide is meant to demonstrate how this can be done with Transifex.
Transifex Native is a collection of tools that allow for easy localization of your applications. Install the provided SDK, push or pull content for localization directly with Transifex without the need for a file.
With this solution Transifex serves a development environment where parallel development and multiple releases are the norm, perfectly matching the current development flow (Continuous Iteration/Continuous Development). Localization becomes a seamless part of the development cycle. Engineers have no delays or additional steps to manage localization. Transifex Native runs in parallel with minimal supervision.
In "SDK Overview"