| id | supported-cultures |
|---|---|
| title | Supported cultures |
| sidebar_position | 5 |
| diataxis | reference |
| persona | application developer |
| example | illustrative |
import coverage from './language-coverage.json';
export const supportedCultures = coverage.locales?.map(({locale}) => locale) ?? coverage.cultures ?? [];
Humanizer 4 treats locale support as all-or-nothing. Every culture listed below supports every applicable localized feature. Regional cultures may reuse a same-language parent, and calendar or numeric formatting may use .NET globalization data when no Humanizer override is needed; neither represents partial support.
Use a culture code from the list with CultureInfo:
using System.Globalization;
using Humanizer;
var culture = CultureInfo.GetCultureInfo("pt-BR");
Console.WriteLine(123.ToWords(culture));This version supports {supportedCultures.length} cultures:
-
{supportedCultures.map((locale) => (
{locale}
))}
A listed culture is supported. Missing behavior, English fallback, or incorrect language in that culture is a bug. If output is wrong, use the correction path.
Open the correction guide or open a prefilled locale issue.
The sibling language-coverage.json is generated separately for each docs
version. Published snapshots use their own verified NuGet packages and culture
lists; they never inherit another version's inventory.