| id | index |
|---|---|
| title | Humanizer documentation |
| slug | / |
| sidebar_position | 0 |
Turn program-shaped values into text people can read. These guides cover Humanizer from a first installation through the most common string, date, number, enum, collection, and localization tasks.
- What Humanizer does — decide where it belongs in an application.
- Install Humanizer — choose a version and add the package.
- Five-minute quick start — run a verified first example.
- Choose the right package — understand the release-specific package layout.
- Troubleshoot Humanizer — diagnose version, 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. The version selector keeps guides, examples, and API pages in the same release.
- Languages and cultures — choose a culture and understand the package boundary.
- Supported cultures — find the culture codes supported by this version.
- 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.
- Plan an upgrade — follow every compatibility boundary between two supported versions.
- Upgrade to Humanizer 4 — review verified differences from
3.0.10. - 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.