Accessing wrong URL results in not loading the correct translation file

[moyounishimself]

Hi there,

I'm using Next 14 with page routing and recently introduced a locale so now I have de and en. One issue I noticed is that when I access a wrong url the locale isn't loaded.

Steps to reproduce:

1. open localhost/this-page-does-not-exist
2. 404 page UI should render with user locale
3. Try switching locale using setLanguage and now it can't find the translation

404-i18n.mp4

It tries to load {locale}/this-page-does-not-exist.json for some reason. Do you have any idea how to fix this? Aside from redirecting to 404 url

[moyounishimself]

Any suggestions? @aralroca

[aralroca]

On pages router you can use /404 to load the namespaces:

next-translate/examples/complex/i18n.js

Line 7 in e636125

'/404': ['error'],

On app router is similar but with /_not-found