Translation and Localization for Tech
Localization of interfaces, product documentation, knowledge bases and in-app content for SaaS vendors. Resource files handled in their own format, with no copy-paste round trip.
What does Asiatis translate for technology and saas?
Asiatis localizes software products: interface strings, documentation, knowledge base, transactional email and in-app content. We work directly in your resource files, which preserves keys, variables and each language's plural rules. Product terminology is fixed once, then enforced across every later release.
Documents handled
Each document type raises a difficulty of its own — and that is what decides how the engagement is organized.
Interface strings
Translated against their space constraint: a German button routinely runs half again longer than the English one.
Product documentation and guides
Living content, republished each release — the delta matters more than the total volume.
Knowledge base and help centre
Written to be found by search: headings must use the words users type, not internal terminology.
Transactional email and notifications
Short texts full of variables, where one broken placeholder breaks the message for every recipient.
Terms of service and privacy policy
Contractual documents: handled as legal text, not as product content.
Release notes and changelogs
Published fast and often; turnaround dominates, and the format is stable.
Industry vocabulary
A few terms where the calque is expensive. They enter the account glossary on the first engagement.
- Téléverser
- Renders "upload". The borrowed "uploader" survives in speech, but a product sold in Quebec writes "téléverser".
- Infonuagique
- Renders "cloud". The official Quebec term, and the one expected in public tenders.
- Authentification à deux facteurs
- Never shortened to "2FA" in a consumer-facing French interface, where the acronym does not land.
- Tableau de bord
- Renders "dashboard". The untranslated "dashboard" survives in poorly localized interfaces and cheapens the product.
Applicable regulatory requirements
What makes translation mandatory in this sector, and under whose authority. We tell you what applies to your situation before the quote, not after the invoice.
Charter of the French Language (Bill 96)
Software offered in Quebec must exist in French where a French version exists elsewhere, and the French version cannot be less functional.
Official source: Charter of the French Language (CQLR c. C-11) — LégisQuébecQuebec Law 25
Privacy policies and consent mechanisms appear in French, in clear and simple terms.
Official source: Act respecting the protection of personal information in the private sector (CQLR c. P-39.1)Accessibility for Ontarians with Disabilities Act (AODA)
Web content of covered organizations meets an accessibility level that must survive translation — alt text gets translated too.
Official source: Accessibility for Ontarians with Disabilities Act, 2005PIPEDA
Privacy notices aimed at Canadian customers outside Quebec follow the federal regime.
Official source: PIPEDA — Justice Canada
Last regulatory review: July 27, 2026. Provided for information only. This is not legal advice. Consult legal counsel for your own situation.
Most requested language pairs
Standard translation rates per word. Certified translation is billed differently and delivered in 2 to 3 business days.
| Language pair | Standard rate per word |
|---|---|
| English ↔ French (Quebec/Canada) | $0.17 – $0.19/word |
| English ↔ Japanese | $0.22 – $0.24/word |
| English ↔ Korean | $0.22 – $0.24/word |
| English ↔ German | $0.18 – $0.20/word |
The full grid is on the pricing page.
A representative engagement
Going French for the Quebec market
An English-language SaaS vendor opens the Quebec market and finds that a partial French version hurts more than it helps. The engagement handles three layers at different rhythms: the interface, fixed and approved once, then maintained as a delta each release; the documentation, picked up continuously; and the contractual documents, handled as legal text. The product glossary is settled before the first interface string, because a term changed later ripples through hundreds of strings.
Sector questions
Do you work inside our resource files?
Yes — JSON, XLIFF, PO, YAML, ARB and the usual formats. Keys, variables and tags stay intact; what breaks interfaces is the copy-paste round trip through a word processor, not the translation.
How do you handle strings that overflow once translated?
We flag overruns rather than truncate. When the space constraint comes with the string, the wording is calibrated on the first pass.
Can you keep up with our release cadence?
Yes, by working on the delta: only new or changed strings go out, with the memory returning the rest. A weekly release cycle is sustainable on those terms.
Do you also translate our marketing site?
Yes, but separately: a website is adaptation, not software localization. The two share the product glossary and nothing else.
A project in this sector?
Send us your documents and your deadlines. You get a quote Quote in 1 business hour, spelling out what is a regulatory obligation and what is not.
Get a quote