i18n | Internationalization - No locale-based routing
Unanswered
nuno posted this in #help-forum
nunoOP
Hey guys, just started a project using
Next.js 14 and want to implement translations on it, but trying to avoid using the internationalized sub-paths/domains suggested on the docs (https://nextjs.org/docs/app/building-your-application/routing/internationalization).
I wonder if is it possible to have a similar approach as the
Any idea or suggestion would be much appreciated.
Next.js 14 and want to implement translations on it, but trying to avoid using the internationalized sub-paths/domains suggested on the docs (https://nextjs.org/docs/app/building-your-application/routing/internationalization).I wonder if is it possible to have a similar approach as the
react-i18next (https://react.i18next.com/) library, with a custom hook (https://react.i18next.com/guides/quick-start#using-the-hook) without using locale-based paths/params.Any idea or suggestion would be much appreciated.
1 Reply
Nelson's Sharp-tailed Sparrow
Im interested in this too