Skip to content

[No QA] Small refinement for internationalization docs #71258

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
luacmartins merged 2 commits into from
Sep 25, 2025
Merged

[No QA] Small refinement for internationalization docs #71258

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
188991e
Small refinement for internationalization docs
roryabraham Sep 25, 2025
547db48
and/or
roryabraham Sep 25, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions contributingGuides/philosophies/INTERNATIONALIZATION.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,14 +29,14 @@ All translations are stored in language files in [src/languages](https://github.
### - Common phrases SHOULD be shared when used in multiple places
A common rule of thumb is to move a common word/phrase to be shared when it's used in 3 or more places.

### - Complex translation strings MUST use arrow function format
Always prefer longer and more complex strings in the translation files. For example, if you need to generate the text `User has sent $20.00 to you on Oct 25th at 10:05am`, add just one key to the translation file and use the arrow function version:
### - Complex translation strings MUST NOT be split up for formatting or value injection
Always prefer to use arrow functions and/or HTML to produce rich text in translation files. For example, if you need to generate the text `User has sent $20.00 to you on Oct 25th at 10:05am`, add just one key to the translation file and use the arrow function version:

```javascript
nameOfTheKey: ({amount, dateTime}) => `User has sent ${amount} to you on ${datetime}`,
nameOfTheKey: ({amount, dateTime}) => `User has sent <strong>${amount}</strong> to you on <a>${datetime}</a>`,
```

This is because the order of phrases might vary from one language to another.
This is because the order of phrases might vary from one language to another, and LLMs will be able to produce better translations will the full context of the phrase. If rich formatting is needed, use HTML in the string and render it with react-native-render-html.

### - Plural forms MUST be handled correctly using plural translation objects
When working with translations that involve plural forms, it's important to handle different cases correctly:
Expand Down
Loading