{"id":89840,"date":"2024-08-05T18:01:39","date_gmt":"2024-08-05T16:01:39","guid":{"rendered":"https:\/\/phrase.com\/?p=89840"},"modified":"2024-10-31T12:56:42","modified_gmt":"2024-10-31T11:56:42","slug":"qwik-localization","status":"publish","type":"post","link":"https:\/\/phrase.com\/blog\/posts\/qwik-localization\/","title":{"rendered":"Mastering Qwik Localization: A Comprehensive Guide"},"content":{"rendered":"\n
\n\n\t\n\t
\n\t\t
\n\t\t\t

As applications become more complex, loading more JavaScript upfront increases client bundle sizes and slows initial load times. Frameworks like Next.js tackle this with Server Components, which render on the server to reduce the client’s payload and browser workload. Qwik<\/a> takes a radically different approach, serializing the application’s state on the server and resuming<\/a> it on the client, which avoids the need for re-rendering and hydration in the browser.<\/p>\n

While Qwik\u2019s instantly interactive \u201cLive HTML\u201d and aggressive lazy-loading can speed up our apps, they make things like internationalization<\/a> (i18n) a bit more tricky. Thankfully, the Qwik Speak<\/a> library by Roberto Simonetti<\/a> simplifies Qwik i18n while adhering to Qwik\u2019s resumability and lazy-loading principles. In this guide, we\u2019ll walk through a Qwik demo app and internationalize it using Qwik Speak. Let\u2019s get started.<\/p>\n

\ud83d\udd17 Resource<\/strong> \u00bb<\/strong> Internationalization (i18n) and localization (l10n) allow us to make our apps available in different languages and regions, often for more profit. If you\u2019re new to i18n and l10n, check out our guide to internationalization<\/a>.<\/p>\n

\n
\n

Overview<\/p>\nToggle<\/span><\/path><\/svg><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n