Skip to main content
Version: 4.0 (next)

Supported cultures

Orientation​

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.

Example​

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 102 cultures:

  • af
  • am
  • ar
  • as
  • az
  • be
  • bg
  • bn
  • bs
  • ca
  • cs
  • cy
  • da
  • de
  • de-CH
  • de-LI
  • el
  • en
  • en-GB
  • en-IN
  • en-US
  • es
  • et
  • eu
  • fa
  • fi
  • fil
  • fr
  • fr-BE
  • fr-CH
  • ga
  • gl
  • gu
  • ha
  • he
  • hi
  • hr
  • hu
  • hy
  • id
  • ig
  • is
  • it
  • ja
  • ka
  • kk
  • km
  • kn
  • ko
  • kok
  • ku
  • ky
  • lb
  • lo
  • lt
  • lv
  • mk
  • ml
  • mn
  • mr
  • ms
  • mt
  • my
  • nb
  • ne
  • nl
  • nn
  • or
  • pa
  • pa-Arab
  • pl
  • ps
  • pt
  • pt-BR
  • ro
  • ru
  • si
  • sk
  • sl
  • so
  • sq
  • sr
  • sr-Latn
  • sv
  • sw
  • ta
  • te
  • th
  • tk
  • tr
  • uk
  • ur
  • ur-IN
  • ur-PK
  • uz-Cyrl-UZ
  • uz-Latn-UZ
  • vi
  • yo
  • zh-CN
  • zh-Hans
  • zh-Hant
  • zu-ZA

Pitfall​

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.

Version notes​

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.