i18n
i18n copied to clipboard
Yet another i18n integration for Astro with server and client utilities, type safety and translations built-in.
Based on header like native i18n feature
Hi! The integration works like a charm with Astro. Now I'm trying to do the next step which is adding a CMS so that clients can handle their multilanguage website...
Currently, we use `addWatchFile` on any route and restart if they change. The DX is pretty bad, especially on larger website. It would be better to use `server` in `astro:server:setup`
Description: Currently, the i18n integration does not support adding links within translated strings. This feature would be very useful for cases where a translated phrase needs to include a link...
### What I did: 1. Created a new Astro project through npm, options > ts: strictest, template: blog, install dependencies ``` npm create astro@latest ``` 2. I've added [I18n for...
Like this ` domains: { fr: "https://fr.example.com", es: "https://example.es" } `
Hi Florian, Wanted to share two instances of discrepancies between the integration and the docs. 1) Integration name from the command line in new project does not match the docs...
So, for example if the path is `/freedom` and you have the locale `fr`, then it will switch to French even if your current locale is English for example. Reproduction...