Internationalization (i18n)
Usage
locale prop.Locale
Use the locale prop with the locale you want to use from pohon-ui/locale:
<script setup lang="ts">
import { fr } from 'pohon-ui/locale';
</script>
<template>
<PApp :locale="fr">
<NuxtPage />
</PApp>
</template>
code property (e.g. en, en-GB, fr) that determines the date/time format in components like Calendar, InputDate and InputTime.Custom locale
You can create your own locale using the defineLocale utility:
<script setup lang="ts">
import type { Messages } from 'pohon-ui';
const locale = defineLocale<Messages>({
name: 'My custom locale',
code: 'en',
dir: 'ltr',
messages: {
// implement pairs
}
});
</script>
<template>
<PApp :locale="locale">
<NuxtPage />
</PApp>
</template>
code parameter, there you need to pass the iso code of the language. Example:hiHindi (language)de-AT: German (language) as used in Austria (region)
Extend locale
You can customize an existing locale by overriding its messages or code using the extendLocale utility:
<script setup lang="ts">
import { en } from 'pohon-ui/locale';
const locale = extendLocale(en, {
code: 'en-AU',
messages: {
commandPalette: {
placeholder: 'Search a component...'
}
}
});
</script>
<template>
<PApp :locale="locale">
<NuxtPage />
</PApp>
</template>
Dynamic locale
To dynamically switch between languages, you can use the Nuxt I18n module.
Install the Nuxt I18n package
pnpm add @nuxtjs/i18n
yarn add @nuxtjs/i18n
npm install @nuxtjs/i18n
bun add @nuxtjs/i18n
Add the Nuxt I18n module in your nuxt.config.ts
export default defineNuxtConfig({
modules: [
'pohon-ui',
'@nuxtjs/i18n'
],
css: ['~/assets/css/main.css'],
i18n: {
locales: [
{
code: 'de',
name: 'Deutsch'
},
{
code: 'en',
name: 'English'
},
{
code: 'fr',
name: 'Français'
}
]
}
});
Automatic locale
When @nuxtjs/i18n is installed, the App component follows the current i18n locale. Only the Pohon UI locales matching your i18n.locales are bundled:
<template>
<PApp>
<NuxtPage />
</PApp>
</template>
language or code, falling back to the base language (for example, pt-BR uses pt_br and en-US uses en). A locale without a match falls back to English. Set the locale prop to override it, for example with a custom locale.Automatic link localization
When @nuxtjs/i18n is installed, the Link component automatically localizes internal links using the $localePath helper. This means you don't need to manually wrap your links with localePath() or localeRoute().
<template>
<!-- Automatically becomes /en/about or /fr/about based on current locale -->
<PLink to="/about">
About
</PLink>
<PButton to="/contact">
Contact
</PButton>
</template>
localePath() or localeRoute() if needed.Dynamic direction
Each locale has a dir property which will be used by the App component to set the directionality of all components.
In a multilingual application, you might want to set the lang and dir attributes on the <html> element dynamically based on the user's locale, which you can do with the useLocaleHead composable. It reads language and dir from your i18n.locales:
export default defineNuxtConfig({
i18n: {
locales: [
{
code: 'ar',
language: 'ar',
dir: 'rtl',
name: 'العربية'
},
{
code: 'en',
language: 'en',
name: 'English'
}
]
}
});
<script setup lang="ts">
const head = useLocaleHead();
useHead(() => ({
htmlAttrs: head.value.htmlAttrs
}));
</script>
<template>
<PApp>
<NuxtPage />
</PApp>
</template>
experimental.strictSeo enabled, @nuxtjs/i18n sets these attributes itself and useLocaleHead must not be called.Supported languages
By default, the en locale is used.
arazbebgbncackbcsdadede-ATde-CHelenen-GBeseteufa-IRfifrglhehihrhuhyidisitjakakkkmkokylbloltlvmnmsnb-NOnlplptpt-BRroruskslsqsvtgthtrug-CNukuruzvizh-CNzh-TW