#when doing internationalisation like in

1 messages · Page 1 of 1 (latest)

alpine oracle
lofty stratusBOT
#

Hi @alpine oracle. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

Sorry @alpine oracle, I seem to be having a bit of trouble. Don't worry though, I've pinged my supprt and they will try to fix me up! :technologist:

Perhaps try again in 15mins?

alpine oracle
#

@lofty stratus when doing internationalisation like in the example with middleware for app router (no next-intl), is there a better way of making the dictionaries avail to components than prop drilling?

lofty stratusBOT
#

Let me check the knowledge base for you. One moment! :books:

#

Hmm, I don't know enough to give you a confident answer yet. However, you can refer to the Next.js documentation on internationalization and i18n-routing for more information:


Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

Add support for multiple languages with internationalized routing and localized content.

Next.js has built-in support for internationalized routing and language detection. Learn more here.