| id | index |
|---|---|
| title | Humanizer documentation |
| slug | / |
| sidebar_position | 0 |
Humanizer 4 turns program-shaped values into text people can read. These docs cover the current package, APIs, and behavior.
- What Humanizer does — decide where it belongs in an application.
- Install Humanizer — add the package to a project.
- Developer quick start — run a small, deterministic example.
- Configuration basics — choose per-call, ambient, or global configuration.
- Troubleshoot Humanizer — diagnose package, culture, parser, analyzer, and AOT problems.
- Find a Humanizer scenario — route from the value you have to the text you need.
- Inflect nouns and render quantities
- Work with dates, times, durations, and ages
- Format numbers, words, byte sizes, and rates
- Humanize enums, flags, and collections
- Configure localization and extensibility
For exact signatures, open the API reference. It is generated from Humanizer 4.
- Languages and cultures — choose a culture and understand localization behavior.
- Supported cultures — find the culture codes supported by Humanizer 4.
- Report or correct a language issue — provide the linguistic and platform context needed for a reliable fix.
- Contribute to Humanizer — follow the locale, validation, and documentation workflows.
- Upgrade from an earlier release — follow the version-specific migration guidance.
- Migrate namespaces with the analyzer — configure and run the bundled analyzer locally and in CI.
- Publish trimmed or Native AOT — choose linker-safe enum APIs and run the publish proof.