Internationalization
Every component accepts a language prop. The widget renders all its UI text in that language, using a translation bundle shipped with fansunited-frontend-core.
Supported languages
| Code | Language |
|---|---|
en | English |
bg | Bulgarian |
de | German |
el | Greek |
es | Spanish |
fr | French |
fr-be | Belgian French |
it | Italian |
pl | Polish |
pt | Portuguese |
pt-br | Brazilian Portuguese |
ro | Romanian |
sk | Slovak |
sr | Serbian |
type LanguageType =
| "en" | "bg" | "de" | "el" | "es" | "fr" | "fr-be"
| "it" | "pl" | "pt" | "pt-br" | "ro" | "sk" | "sr";Per-component usage
import { ClassicQuizPlay } from "fansunited-frontend-components";
<ClassicQuizPlay
entityId="quiz-123"
sdk={sdk}
template={WidgetTemplate.STANDARD}
language="pt-br"
/>Phone country code fallback
Components that include phone fields (lead forms) use the language code to pick a sensible default phone country if none is provided. For example, language="bg" defaults the phone country code to +359. You can override it explicitly with phoneCountryCode in LeadsOptions.
Custom labels (per component)
A handful of components expose labels props for fine-grained text overrides — useful when you want to localize a single button or title beyond the built-in translations.
CollectLead→LeadLabelsBetslip→BetslipLabels
See each component page for the full label shape.