🌎
Internationalization
DSFR components contain hard coded strings.
These strings can be switched from a langage to another with a provider.
When lang="en"
When lang="fr"
Integration with i18n libraries
i18nifty
Next.js i18n App Router
Next.js i18n Page Router
Other i18n library
i18nifty
A type safe internationalisation library for SPAs and Next.js
import { useLang } from "i18n";
startDsfrReact({
defaultColorScheme: "system",
useLang
});
DISCLAMER: I'm the author of i18nifty.
While I can confidently recommend it for SPAs, I have to warn you that using i18nifty in Next.js will force you to opt out from Automatic Static Optimization and bundle all your translations in the JavaScript bundle. SSR, SSO will work fine though.
Routing: Internationalization
At the bottom you have setup examples
Assuming you have configured Next so that you have a lang prop provided to you in the main layout:
app/[lang]/layout.txs
import { i18n } from '../../i18n-config'
export async function generateStaticParams() {
return i18n.locales.map((locale) => ({ lang: locale }))
}
export default function Root({
children,
params,
}: {
children: React.ReactNode
params: { lang: string }
}) {
const { lang } = params;
return (
<html
{...getHtmlAttributes({ defaultColorScheme, lang })}
>
<head>
{/*...*/}
</head>
<body>
<DsfrProvider lang={lang}>
{/*...*/}
</DsfrProvider>
</body>
</html>
);
}
Assuming you have enabled internationalized routing:
pages/_app.tsx
import { useRouter } from "next/router";
const { withDsfr, dsfrDocumentApi } = createNextDsfrIntegrationApi({
"defaultColorScheme": "system",
Link,
useLang: () => {
const { locale = "fr" } = useRouter();
return locale;
}
});
It's up to you to replace in the following example
"fr" by the desired locale using to tooling exposed by your i18n library.startDsfrReact({
defaultColorScheme: "system",
useLang: () => "fr"
});
The components usually come with one or two translations by default, typically english (
en), spanish (es) and sometime german (de). Illustration with the <DarkModeSwitch /> component.You can add translation for extra language on a component basis, like so:
import { addAlertTranslations } from "@codegouvfr/react-dsfr/Alert";
addAlertTranslations({
lang: "zh-CN",
messages: {
hide message: "隐藏消息"
}
});
The above code adds chinese (
zh-CN) support for the Alert component. You can call addAlertTranslations() wherever, just be sure it's evaluated before the first use of the component, here <Alert />.You can also use this approach for overwiting the default text. Example:
import { addDisplayTranslations } from "@codegouvfr/react-dsfr/Display";
addDisplayTranslations({
lang: "fr",
messages: {
"dark theme": "Thème sombre 🤩",
}
});
It goes without saying this is not a recommended customization of the Display Modal
When utilizing Next in App Router mode, it's crucial to accurately add or overwrite translations at the proper location.
For components that you use as server components, such as
<Header />, <Footer />, or the <Display /> modal, you should make calls to addXxxTranslation within app/layout.tsx.Last modified 1mo ago