The pull request from globalize.now is the first time you see real output. If something looks off, most fixes are a project setting or a tab, not a support ticket.
Fastest fix of all: edit the translation in the PR diff. Your edit becomes the approved version and goes into the translation memory, so it's reused next time and never re-translated.
The translations sound wrong or unnatural
-
Wrong tone (too formal, too casual, wrong register): open Project → Style Guides and set the tone and formality for that language (for example du vs Sie, tu vs usted). If the language has no style guide yet, the dashboard drafts one from your own source content in one click; edit and save. The next job follows it.
-
Brand terms, product names or legal wording translated: add them to Project → Glossary with the required translation (or "keep in English") per language. Glossary terms are protected during translation. You can import a list in bulk.
-
Idioms translated literally: fix the string in the PR, and add a note in the language's style guide about how you want that kind of phrase handled.
-
The same string translated differently in two places: the translation memory reuses approved translations. Approve the version you want (edit it in the PR, or push it to the repo), and it wins from then on.
Details on all four tools: How do I control tone, terms and quality?
The translations are empty or contain key names instead of text
If a locale file contains "" or key names like "checkout.submit": "checkout.submit", the translation job didn't run or failed.
-
Open the project dashboard and check the job for this PR. A failed job shows its error and can be retried.
-
Check Project → Settings → Repository → Watched branches: the branch you pushed to has to be on the list for a job to start automatically. Or run a manual job on that branch from the dashboard.
-
If credit has run out, translations pause and the app says so — see How is billing calculated?
The PR is missing strings from my app
If some strings are translated but others are still hardcoded, the conversion missed them.
Common reasons: strings inside config objects (form labels, error messages, toast notifications); strings in files changed after the conversion ran; deeply nested component patterns.
Fix: in your coding agent, ask it to finish wrapping the strings it missed:
wrap the remaining hardcoded strings
The agent re-scans, adds the missing keys without duplicating existing ones, and your next push to a watched branch translates them.
Wrong strings are being translated
If URL slugs, database field names or internal identifiers show up as translated strings, the wrong content was extracted.
Open your source locale file and remove the keys that shouldn't be there. Then tell your agent:
Do not translate strings in [path/to/file.ts]
The PR changes files I didn't expect
A translation PR only contains locale files. If you see other changes, it's usually locale files placed in a non-standard location during setup: review the diff, merge what's correct, move files to where you want them and update the locale path patterns in project settings.
If something looks completely wrong, close the PR without merging — your default branch is untouched. Then chat with us at globalize.now with the PR link and we'll review what happened.