# i18n **This is a server SDK — it does not render translated strings itself.** There is no `t()` / label-render helper in the Swift SDK. Translation rendering is a **client-side** concern: the browser SDK fetches the translation profile and renders labels via its own `t()`. What the Swift server SDK does is emit the SSR loader/bootstrap ` ``` `bootstrapScriptTag` also accepts `i18nProfile:` (to set `data-i18n-profile`) and `baseURL:` (defaults to `https://cdn.shipeasy.ai`). ## The cross-SDK story 1. **Server (Swift):** emit `bootstrapScriptTag` + `i18nScriptTag(clientKey, profile: "{{PROFILE}}")` into ``. 2. **Browser (`@shipeasy/sdk` client):** the loader hydrates the profile; your front-end calls the client SDK's `t("some.key")` to render the actual translated string. So the Swift SDK is the *delivery mechanism* for the loader/bootstrap; the *rendering* (`t()`) happens in the browser client SDK against the `{{PROFILE}}` profile.