Languages and cultures
Orientation
Humanizer localizes behavior by culture, not by translating one final string. Choose a culture for the operation, then confirm that it is listed for the selected documentation version. Every listed culture supports every applicable localized feature.
The package and the culture are separate choices. Published releases through
3.0.10 use the Humanizer metapackage to bring in Humanizer.Core and its
locale packages. Humanizer 4 is consolidated: one
Humanizer reference contains the runtime, generated locale data, and
analyzers. Installing a culture-specific package does not select that culture,
and selecting a culture does not install a missing historical package.
Example
This complete example selects French explicitly:
using System.Globalization;
using Humanizer;
var french = CultureInfo.GetCultureInfo("fr-FR");
Console.WriteLine(42.ToWords(french));
Use culture selection for per-call and ambient-culture patterns. Use supported cultures for the selected-version inventory. Use the scenario finder to reach the focused guide for number words, dates, clock notation, collections, or another localized task.
Found a wrong translation, inflection, parser result, or platform-specific format? Follow the language correction guide or open a prefilled locale issue.
Pitfall
Do not infer support from a package name or English fallback. A regional
culture can reuse a same-language parent such as fr; that is an
implementation detail, not partial support. Report incorrect inherited
behavior just as you would incorrect directly authored behavior.
Version notes
The generated coverage page is scoped to the selected documentation version.
Stable snapshots use their own package and documentation evidence. Package
consolidation is Humanizer 4 behavior, while published versions through
3.0.10 retain the metapackage and locale-package model.