Aral Roca Gomez
Aral Roca Gomez
@mkbctrl I see that in theory they support next-translate https://github.com/lokalise/i18n-ally/blob/435df209ec85bd43181a24635f268dce9d591c90/package.json#L826 not sure about their implementation. I will try to fix it and PR in their repo 👍
In my case, I solved it by adding it to the SVG. But it's a very ugly workaround... Adding this after `qrCode.update(optionsToUpdate)`: ```js setTimeout(() => { ref.current.lastChild.innerHTML += `${text}`; },...
> Apologies for the off topic point, @aralroca can you tell me how you prepped the js file size / names to go into that Voronei map? I use Webpack...
Probably you can do it using the `loadLocaleFrom` config function, that is just to get more flexibility in order to load the translations.
No, you should implement fallbacks, example: ```js { "loadLocaleFrom": async (lang, ns) => { const translationsEnGb = await import(`./locales/en-gb/${ns}.json`).then((m) => m.default) if (lang === 'en-gb') return translationsEnGb; const translations =...
@rolandjlevy Instead of 2.0.5 try the latest version of next-translate & next-translate-plugin
For me make sense to change the URL to the correct language. However maybe you can consider instead of doing it in a `useEffect` do these redirects in a [middleware](https://nextjs.org/docs/app/building-your-application/routing/middleware),...
`setLanguage` is not doing any extra magic, is using the `router.push` from `next/router`: https://github.com/aralroca/next-translate/blob/de5ad45d005488b36f21fed291e18437af468972/src/setLanguage.tsx#L3-L15 Probably is changing to the domain that you have defined inside [`domains`](https://nextjs.org/docs/pages/building-your-application/routing/internationalization#domain-routing), but this is part...
Same issue in `@angular/cli: 1.0.0-beta.32.3`! 😟