Documentation
Everything you need to translate your software with PTC (Private Translation Cloud): repository integrations, supported file formats, the PTC API, and how PTC reviews translations in context.
Using PTC
- Getting started Two ways to start with PTC: connect your coding agent through the PTC MCP and let PTC handle everything, or set up the project yourself in five steps.
- Supported formats and languages PTC translates PO, JSON, YAML, Android XML, Apple .strings, .stringsdict, .xcstrings and .plist, Java .properties, CSV and XLIFF. See an example of each.
- Brand voice, glossary and terminology To keep brand terms and tone, AI translation needs your glossary, your product's context and your style guide. PTC applies all three to every translation.
- AI Visual QA PTC's AI Visual QA scans screenshots of your translated interface, catches localization problems, and fixes them before users ever see them.
-
API reference
The PTC API uses REST and allows you to integrate software localization into your development process.
- Find Supported File Formats and Languages via the API Use these API endpoints to discover what source file formats and target languages your PTC project supports before creating translation jobs.
- Upload and Manage Source Files via the API Use this API to upload new source files, replace outdated ones, track translation progress, and download completed translations.
- Request and Retrieve Translations via the API Use this API to send content for translation, track its progress, and retrieve the translations in all target languages.
Good practice
- Prepare your software for translation Learn software localization best practices: prepare code, handle dynamic content, and create flexible UI layouts for global markets.
- Prevent long translations from breaking layouts Translated UI text is often longer than English (German by about 30%) and overflows buttons and menus. See how to design, test and translate so it fits.