01 Technical translation · New Canaan, CT
You’ve done the hard part: the device works, the app is stable, the manual is signed off. Now get every button, every warning and every IFU page into Spanish, Portuguese and French — certified, glossary-locked, and checked on the real screen before your release goes out.
Rather talk it through? (203) 966-5655 · by appointment
1 string over limit → screenshot filed in your tracker
02 Project pricing
You pay per project — one fixed number, agreed before work starts, based on your actual files. Every quote names your linguist pairing, your timeline and exactly what lands back in your repo.
Rolling out something bigger — a 400-page DITA set, a five-locale launch? Call (203) 966-5655 and scope it with us.
$1,480per language
Lock your terminology before a single string gets translated. You walk away with the reference every future release builds on.
from$4,350per language
Your interface and your user manual, translated, revised and reviewed inside your running build — ready for launch day.
from$6,280per language
IFUs, labeling and patient-facing material for the regulator who will read every word. Built to be filed, not just read.
→ Your next step
03 How we run it
Most translation errors aren’t grammar — they’re context. A linguist who’s never seen your interface has to guess. Ours don’t: every project runs off a locked glossary and finishes with a review inside your build. We’re small enough that your glossary has an owner, not a ticket number.
Your linguist reviews “Étalonnage terminé” where your user will read it: on the device, at real font size. If it clips, we catch it here — not your field team.
You show us the files, the locales and the date. You hear what’s realistic before you commit a dollar.
20 minWe extract your terms, propose targets, and your in-market reviewer signs off once — then it’s law for every string.
6–8 daysOne linguist translates, a second revises every segment against source and glossary. Length limits get checked as we go.
Per scopeWe review in your staging build, TestFlight or APK and file screenshot-backed issues straight into your tracker.
1 round incl.XLIFF back as XLIFF, IDML back as IDML. Certified documents ship with a signed certificate of accuracy.
Your format04 The length check
Spanish, Portuguese and French usually run longer than your English source. Buttons sized for English truncate, toasts wrap, labels spill past the housing. You get every string checked against the limits you give us — before your users find the problem.
| String ID | EN source | Max | ES (es-MX) | PT-BR | FR (fr-FR) | Verdict |
|---|---|---|---|---|---|---|
| btn.save | Save4 chars | 10 | Guardar7 | Salvar6 | Enregistrer11 · +1 | FR over · widen button |
| alert.battery_low | Battery low11 chars | 24 | Batería baja12 | Bateria fraca13 | Batterie faible15 | All fit |
| label.do_not_reuse | Do not reuse12 chars | 18 | No reutilizar13 | Não reutilizar14 | Ne pas réutiliser17 | All fit |
| menu.settings | Settings8 chars | 12 | Configuración13 · +1 | Configurações13 · +1 | Paramètres10 | ES / PT · approved short form |
| toast.sync_done | Sync complete13 chars | 20 | Sincronización completada25 · +5 | Sincronização concluída23 · +3 | Synchronisation terminée24 · +4 | Rewrite all three |
05 What it costs to skip this
You’ve probably seen at least one of these. Every one of them is cheaper to prevent than to patch after launch.
Your French user taps the one button that matters and reads “Enregistr…”. You hear about it from a support ticket three weeks after launch.
In-context LQA on your staging build — every screen, every locale, screenshot-backed.
Page 4 of your Spanish IFU says “cánula”. Page 19 says “tubo”. A reviewer notices, and your submission timeline stretches while you explain.
A glossary locked before translation starts, enforced on every page and every revision after.
Your strings arrived as a bare spreadsheet. The translator read “Clear” as the adjective, not the action — and your Spanish delete button now reads like “obvious”.
String IDs, screenshots and developer notes travel with every segment. Nobody guesses.
→ This quarter, not next year
06 Before you call
Our certified translations come with a signed certificate of accuracy from Fairweather & Lowe, stating the translation is complete and true to the source. If a specific authority requires a sworn or notarized translator in-country, flag it on your scoping call — we’ll scope that route explicitly before you pay anything.
You choose: es-MX, es-US or es-ES; pt-BR or pt-PT; fr-FR or fr-CA. Selling across Latin America? We can build one neutral Spanish base plus small locale overrides, so you’re not paying for the same string three times.
For in-context LQA, yes — a staging URL, TestFlight, an APK or an emulator image. Under NDA, with access removed at hand-off. If access isn’t possible, send full-resolution screenshots and we’ll review against those instead.
You send the delta. We run it against your translation memory, so unchanged and repeated strings cost you far less than new ones. Update batches start at $385 and usually turn around inside a week.
Call us today and find out. Small UI sets often fit inside a rush window (+30% of the fee). A full regulatory set usually doesn’t — and we’ll tell you straight rather than promise a date we can’t hold.
07 Book a call
Twenty minutes. You tell us the release date, the locales and what’s in the folder. You hang up knowing your scope, your timeline and your price range — then you decide.
Invoiced per project. Pay by ACH, check, Visa, Mastercard or Amex.
