Spanish · Brazilian Portuguese · Vietnamese — from Spring, TX
a nurse in recife taps ‘começar’, and your welcome email is already waiting — in portuguese that sounds like home.
We translate and culturally localize your UI strings, help-center articles and onboarding emails into Spanish, Brazilian Portuguese and Vietnamese — one fixed package price, $400 to $1,450, agreed before a single key is touched.
fig. 01 — one button, four lengths. English is the shortest your label will ever be; we fit every translation to the space your designer actually drew.es · pt-br · vi
Before we translate a word
your strings, read on the screen they live on
Most string files arrive as a spreadsheet of orphans — “Save,” “Back,” “You’re all set!” — with no clue where they appear. So the first thing we do is click through your product, from a staging login or a folder of screenshots, and give every key an address: which screen, which component, how many characters it’s allowed. Only then are the Spanish, Portuguese and Vietnamese written, each for that exact spot.
3languages — es · pt-br · vi
3kinds of copy — UI, help center, email
$1,450top of the range; packages start at $400
placeholders come home untouched{first_name}, %d and <b> tags are checked line by line before hand-back, so nothing breaks when you merge.
vietnamese tone marks, tested in your typefaceIf your font can’t draw ‘ữ’ or ‘ặ’, you hear it from us — not from a user staring at an empty box.
one glossary per product“Workspace,” “seat,” “billing cycle” are settled once, then reused on every package after, so release four sounds like release one.
the desk that wrote it answers for itQuestions reach the same people who translated your strings, Mon–Fri 8:30am–4:30pm Central, at (213) 564-1506.
The welcome kit
what to tuck into the first email
Send whatever you have and we’ll politely chase the rest. These five make the quote exact.
string filesany export your repo already makes
.json.po.xliff.stringsstrings.xml
screenshots or a staging logina read-only test account is perfect
help articles & emailsMarkdown, HTML, or your help-desk / email-tool export
words that never changeproduct names, feature names, legal lines
your freeze datewe plan the package backwards from it
Every package follows the same path, so you always know which part of the work is happening and who has the file.
A · context pass
every key gets an address
We walk your staging build or screenshots, tag each string with the screen it lives on, and flag the tight ones — tab labels, push notifications, toast messages, and the narrow button your designer swore would never change. Translators then work from a map of your product, not a column of loose words.
B · intake
you send, we size it
Files, screenshots, a freeze date. We count the words, pick the package that fits and send one fixed price — nothing is invoiced until you say yes.
C · translate & localize
written, not converted
Formality is decided with you once — tú or usted, você, bạn or anh/chị — then kept. Dates, currency and number formats follow each market.
D · screen check
back on the screen
We review the translated build or fresh screenshots and catch the overflowing button, the clipped toast, the email subject that cuts off in an inbox preview — then fix it before you ever see it.
E · hand-back
ready to merge
Files return in the format they arrived — same keys, same placeholders — with your glossary and a one-page notes sheet for whoever runs the next release.
The packages
three sizes, each priced before we begin
Prices are per language. Adding a second language to the same files? We’ll quote it in the same reply.
For a feature or fix-up
the patch
$400per package
Up to 1,200 words of UI strings, or a 4-email onboarding sequence
You can, and as a first draft it isn’t bad. What it can’t see is the screen: it doesn’t know “Save” is a nine-character button, that “Post” means a blog entry, or which Vietnamese pronoun your users expect. If you already have machine drafts, send them — we’ll review rather than start over, and price the package to match.
which spanish? which portuguese?
Latin American Spanish and Brazilian Portuguese by default. Castilian Spanish or European Portuguese on request — tell us at intake and we’ll hold to it across every package.
what file formats do you take?
JSON, YAML, .po/.pot, XLIFF, iOS .strings and .stringsdict, Android strings.xml and CSV for the app; Markdown, HTML or your help-desk export for articles; your email tool’s export for onboarding sequences. Files go back in the same format.
how long does a package take?
A patch usually takes about a week; the full lantern runs closer to two or three, depending on article count and how quickly screenshots arrive. Your freeze date goes on our calendar at intake, and we plan backwards from it.
what if a string reads wrong after launch?
Send us the screenshot. Corrections to our own translations within 30 days of hand-back cost nothing — consider it handled.
Where the desk is
spring, tx
167 Pinto Point Place, Spring, TX 77389. Visits by appointment — almost everything happens over email and screen-share.