Fill in these first
- Source text: [paste]
- Target language and market: [e.g. Hindi for users across North India, or Spanish for Mexico]
- Content type: [e.g. app onboarding screens, a job post, a signup form]
- Brand's chosen approach, if any: [e.g. rephrase to avoid gender first, then use both forms, never symbols such as @ or x]
- Space limits: [e.g. buttons under 20 characters]
Task
Translate the text so that it reads naturally and includes every reader, using the approach given, or recommend one if none is given.
Output format
- Recommended approach for this language and content type, in three lines, with the reason.
- Translation, with each gender choice marked in brackets the first time it appears.
- Table: | Source phrase | Gendered translation | Neutral option | Trade-off |
- Techniques used, such as addressing the reader directly, using the action instead of the person, a collective noun, or both forms, with one example each.
- Lines where neutral wording broke the space limit, with a shorter option.
- Five style rules for future translators in this language.
Rules
- Natural grammar comes first; never invent forms that native readers would find wrong.
- Where the source refers to a specific person whose gender is known, keep it.
- Flag any choice that depends on regional usage for a native reviewer.






