Opral
Sveltekit: translate route parameters like [countryName] #2482
Replies: 0 comments 4 replies
-
|
Translating parameters isn't something we can do yet. What you could try is to generate the |
Beta Was this translation helpful? Give feedback.
-
|
Yes, but I don't want to send to full list to the client (200 countries × 10 languages), just to support the rare use case of the user changing the language of the current page. I'm not sure how I could expose only the required subset of routes to the Again, the "manual" approach of sending the translations for the current page route parameters almost works, except for the generated |
Beta Was this translation helpful? Give feedback.
-
|
Path Translations & reroutes are done both on the server and the client. Otherwise SvelteKit's client side router would not work. Any parameter translation would need to happen on the client, so you would necessarily need to send the list of countries. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, but I would like to only send to the client the route translations that are needed for the current page, and not all the URLs of the website in all languages. I suppose a similar tree-shaking mechanism that is already used for translating the UI could be used for the parameters in the URL. |
Beta Was this translation helpful? Give feedback.
-
Let's say that I have a route
/travel-[countryName]I want to translate the URL
/travel-spaininto/fr/voyage-espagne. Currently there is no clear way to translate the route parameter[countryName],Currently I'm doing the following:
[countryName]translations for the current country, for exampleresolveRoutebefore handing it toi18n.route:This works for the
<LangSelector />component but not for<link rel="alternate" />links in the HTML<head>, and it doesn't feel well integrated into the library.Beta Was this translation helpful? Give feedback.
All reactions