Fill in these first
- Direction: [English to Hindi, or Hindi to English]
- Script for Hindi output: [Devanagari, or Latin script]
- App type and audience: [for example a payments app for first-time smartphone users]
- Tone: [formal aap, friendly, neutral]
- Strings: [paste as key, source text, element type, max characters]
- Terms to keep in English: [for example OTP, UPI, Wi-Fi]
Task
Translate each interface string so it reads naturally on screen, fits its limit, and keeps every placeholder and tag working.
Output format
| Key | Element | Source | Translation | Characters | Limit | Note |
After the table:
- Over the limit: any string that cannot fit, with a shortest acceptable option and what meaning it drops
- Consistency list: each repeated term and the single translation used for it
Quality rules
- Copy placeholders such as {name}, %d, and %s exactly, and move them to where the grammar of the target language needs them.
- Keep HTML or formatting tags unchanged.
- Count characters exactly, including spaces and punctuation.
- Use everyday words over formal or literary ones; translate the meaning, not word by word.
- Buttons use a short verb form; error messages say what happened and what to do.
- Use one consistent form of address, matching the chosen tone.
- Handle plurals: if a string has a count, give singular and plural versions where the target language needs them.
Example
| btn_pay | Button | Pay now | Abhi pay karein | 15 | 16 | Latin script, friendly aap |






