In this post, I'll guide you through the process of setting up internationalization (i18n) in a Next.js project. We'll explore how to integrate i18...
For further actions, you may consider blocking this person and/or reporting abuse
Great article 👍 is there a reason you didn't use ParaglideJS?
Nice library but does it support NextJS with output: export?
Going through the library, I found it relatively new and no built in support for NextJS output export. So we are good with next-translate that is minimalist and well maintained but yeah we can give it a try.
Hi, Paraglide Maintainer here
Paraglide does work with NextJs's
output: exportset, but I see that you've already made up your mind.next-translateis certainly a good choice & you won't regret choosing it. We're going to keep working on Paraglide & hopefully it's going to be feature-complete enough next time!Certainly! If it proves to be helpful, we'll definitely consider incorporating it into our project. Thank you! 👍
Will this work on nextjs 12?
Nardos, not sure about it. We can give it a try
@ikramdeveloper Great article. Is it possible to use Trans from next-i18next or any other approach to put custom translated text into the page?
Silvio, I haven’t used
next-i18nextas described in the article. Instead, with thenext-translatepackage, there’s a useTranslation hook that helps in writing custom translated text.