The short answer
Send versioned strings, screenshots, interaction context, placeholder rules and UI constraints. Preserve keys and technical structure, then check the translation in the application.
Context determines meaning
“Save” can describe storing data or a marketing discount. Identify whether a string is a button, heading, error, help message or feature name.
Explain what the user has just done and what should happen next. A context column and screenshot are often more useful than an isolated word list.
Prepare an integration-ready brief
- Current resource files in the expected structure.
- Screenshots or appropriately scoped preview access.
- Key descriptions and ambiguous contexts.
- Approved names and terms that must remain unchanged.
- Length or line-break constraints where applicable.
If strings are exported to a spreadsheet, confirm the re-import process and keep identifiers stable.
Protect placeholders
Android Developers — Localize your app describes resource localization and marking text that must not be translated. Establish equivalent rules for your own file format.
For example, “Hello, {name}” may become “Xin chào, {name}” while {name} remains intact. Ask developers how plurals and parameters work rather than assuming every language can use the same sentence fragments.
Review in the interface
Check truncation, long buttons, parameter combinations and incomplete messages after import. A sentence that reads well in a spreadsheet may fail on screen.
Report the screen, string key, screenshot and expected behavior. Distinguish linguistic corrections from integration defects while tracking both through resolution.
Plan recurring releases
Identify added, changed and retired strings for each release. Explain changes in behavior even when the source wording remains the same.
Agree a content freeze and a terminology approver. Flag unresolved strings in the handover so the product team knows which items need confirmation.
Frequently asked questions
Is a spreadsheet enough?
It can be if it retains identifiers, context and an agreed import method. Screenshots reduce ambiguity.
Will translators change source code?
That depends on the agreed scope. Language work should preserve specified structure and technical elements.
References
Project checklists and examples are written by LocalizeZone. Linked references support the specific statements marked in the article.
Discuss your project
Send sample strings, screenshots and target languages. We can agree handling rules and the scope of interface review.