Skip to content
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

Jump to bottom

Describe relation between region locale and country locale when a country is not found #37745

Merged
merged 3 commits into from
Jun 20, 2022
Merged

Describe relation between region locale and country locale when a country is not found #37745

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
18c4855
Update i18n-routing.md
eric-burel Jun 16, 2022
fe44158
lint-fix
ijjk Jun 20, 2022
860fa92
Merge branch 'canary' into patch-6
ijjk Jun 20, 2022
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
3 changes: 3 additions & 0 deletions docs/advanced-features/i18n-routing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,9 @@ Generally a Locale Identifier is made up of a language, region, and script separ
- `nl-NL` - Dutch as spoken in the Netherlands
- `nl` - Dutch, no specific region

If user locale is `nl-BE` and it is not listed in your configuration, they will be redirected to `nl` if available, or to the default locale otherwise.
If you don't plan to support all regions of a country, it is therefore a good practice to include country locales that will act as fallbacks.

```js
// next.config.js
module.exports = {
Expand Down