next-intl for me

why?

- It's nextjs first as a principle: https://next-intl-docs.vercel.app/docs/design-principles#nextjs-first
- It supports (unstable) static generation, which many others do not
- It supports localized slugs (localized pathnames) e.g. en/hello -> es/hola whihc many others don't
Used it in bigger projects and i was satisfied / good experience

Ok, great answer. And for the translation, is it manual?

Good question and one of the biggest advantages of all:
It has its own visual code extension with a deep-l integration so you can just rightlick on a language -> translate and deep-l does it pretty good (and fully automated)

Ok it's look cool, and what about the price?

opensource / free

Ok, I think you've convinced me, I'm going to try it. thank you very much for your feedback.

you welcome

@American Crow hello 👋, i have a question for implemant deepL on next js 14/ next-intl what you use ? I can't find any resource for that ?

It's integrated in the Vs code extension (i18 ally) https://next-intl-docs.vercel.app/docs/workflows/vscode-integration