Skip to content

Conversation

@soheilnikroo
Copy link

@soheilnikroo soheilnikroo commented Feb 7, 2026

Update the internationalization doc, add an optional function to use for replacement

Fixes #89668

@nextjs-bot nextjs-bot added the Documentation Related to Next.js' official documentation. label Feb 7, 2026
@nextjs-bot
Copy link
Collaborator

Allow CI Workflow Run

  • approve CI run for commit: 6f5377f

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

@icyJoseph
Copy link
Collaborator

icyJoseph commented Feb 9, 2026

A couple of things here. The guide, AFAIK, was meant to be minimal, foundational if you will, covering routing and dictionary loading. We do list a number of libraries and examples that extend the guide.

If I understand correctly, you want to showcase interpolation, but then, the question is, why not add pluralization, nested key access, and expand into ICU Message Format... suddenly the guide is a mini library for i18n.

Each of the libraries and references added in the guide, develops these concepts in full detail, for instance next-intl does that here: https://next-intl.dev/docs/usage/translations

I say this, because, the PR is also making an assumption about the {{placeholder}} convention. It is never explained nor put to use, nor any potential edge cases, or what to do if the value for a placeholder is not passed, etc... it is not a trivial topic.

Also, the guide is using nested objects for scoping, like {products: { cart: "" }}, but the suggested implementation would not be able to handle those right?

I think we should close the PR as it is right now. Let's develop the issue you opened first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Documentation Related to Next.js' official documentation.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Docs: internationalization app router

3 participants