Localization file translation in Canada
XLIFF, JSON, PO and app strings.
Translation of the string files behind software, apps and platforms, with placeholders and variables left intact.
How we handle it
Software text lives in files such as XLIFF, JSON or PO, mixed with variables and tags that must not change. A translator works on the readable text and keeps the code around it untouched.
Send the file, a short note on where each string appears (button, error message, menu) and any style guide for your product. Context avoids mistakes.
Files we translate
- XLIFF files
- JSON and PO files
- App and software strings
- Translation memory exports (TMX)
- Help centre and in-app messages
Who it is for
What to watch for
- Placeholders: variables and tags in the text stay exactly as written.
- Context: a word such as Save or Close needs to be translated for its place in the screen.
- Updates: send only new or changed strings in later rounds to keep the vocabulary consistent.
Other file formats
Contracts, certificates, reports and scanned records.
Word
Letters, contracts, manuals and reports in .docx.
Excel
Price lists, budgets, catalogues and data tables.
PowerPoint
Sales decks, training and conference slides.
InDesign
Brochures, annual reports and catalogues.
Subtitles
SRT and VTT files for video in English and French.
Websites
Pages, menus, metadata and CMS exports.
Frequently asked questions
Will placeholders and variables stay unchanged?
Yes. Variables and tags are left as they are, and only the readable text is translated.
Can you reuse my translation memory?
If you have an existing translation memory or glossary, send it with the files and we follow it.
Need a professional translation?
Request a free, no-obligation quote. A member of our team replies within 12 hours.