|
8 | 8 | **The easiest way to translate your Next.js apps *(with pages setup)*.** |
9 | 9 |
|
10 | 10 | If you are using next-i18next *(pages directory)* in production and like to unleash some super powers, you may have a look at [this blog post](https://locize.com/blog/next-i18next/). |
11 | | -[](https://locize.com/blog/next-i18next/) |
| 11 | +[](https://locize.com/blog/next-i18next/) |
12 | 12 |
|
13 | 13 | If you're using Next.js 13/14/15/16/etc... with App Router, there is no need for next-i18next, you can directly use i18next and react-i18next, like described [in this blog post](https://www.locize.com/blog/i18n-next-app-router). |
14 | | -[](https://www.locize.com/blog/i18n-next-app-router) |
| 14 | +[](https://www.locize.com/blog/i18n-next-app-router) |
15 | 15 |
|
16 | 16 | ## What is this? |
17 | 17 |
|
@@ -451,7 +451,7 @@ Are you trying to generate a [static HTML export](https://nextjs.org/docs/advanc |
451 | 451 |
|
452 | 452 | But there's a way to workaround that with the help of [next-language-detector](https://github.com/i18next/next-language-detector). |
453 | 453 | Check out [this blog post](https://locize.com/blog/next-i18n-static/) and [this example project](./examples/ssg/). |
454 | | -[.jpg)](https://locize.com/blog/next-i18n-static/) |
| 454 | +[](https://locize.com/blog/next-i18n-static/) |
455 | 455 |
|
456 | 456 | ### Translate in child components |
457 | 457 |
|
@@ -513,7 +513,7 @@ This project follows the [all-contributors](https://github.com/kentcdodds/all-co |
513 | 513 |
|
514 | 514 | Needing a translation management? Want to edit your translations with an InContext Editor? Use the original provided to you by the maintainers of i18next! |
515 | 515 |
|
516 | | - |
| 516 | + |
517 | 517 |
|
518 | 518 | With using [locize](http://locize.com/?utm_source=next_i18next_readme&utm_medium=github) you directly support the future of i18next and next-i18next. |
519 | 519 |
|
|
0 commit comments