rsnext/examples/with-next-translate/i18n.json

{
  "locales": ["en", "ca", "ar", "he"],
  "defaultLocale": "en",
  "pages": {
    "*": ["common"],
    "/": ["home"]
  }
}
Add example with next-translate (#13511) Motivated by the need to deploy static sites while having a good i18n support¹ ² @vinissimus developed [next-translate](https://github.com/vinissimus/next-translate). Here's the example ;) References: 1. https://github.com/vercel/next.js/discussions/10651 2. https://github.com/vercel/next.js/pull/12535#issuecomment-624317275 2020-05-28 23:31:05 +02:00			`{`
Add RTL to with-next-translate example (#22808) ### Arabic/Hebrew RTL to `with-next-translate` Example Added a simple example to change HTML direction based on the currently selected language ### References: - [#19049](https://github.com/vercel/next.js/discussions/19049) - [#18667](https://github.com/vercel/next.js/issues/18667) 2021-03-08 01:33:42 +01:00			`"locales": ["en", "ca", "ar", "he"],`
Update next-translate example to support Next 10 with i18n routing (#18480) Co-authored-by: Joe Haddad <joe.haddad@zeit.co> 2020-11-03 15:48:26 +01:00			`"defaultLocale": "en",`
Add example with next-translate (#13511) Motivated by the need to deploy static sites while having a good i18n support¹ ² @vinissimus developed [next-translate](https://github.com/vinissimus/next-translate). Here's the example ;) References: 1. https://github.com/vercel/next.js/discussions/10651 2. https://github.com/vercel/next.js/pull/12535#issuecomment-624317275 2020-05-28 23:31:05 +02:00			`"pages": {`
			`"*": ["common"],`
			`"/": ["home"]`
			`}`
			`}`