Contribute to Humanizer documentation and languages
These pages describe the contributor workflow for v4 development on main.
Start with the smallest path that matches the problem:
- Wrong or awkward output: report a language issue.
- Locale behavior needs code or YAML changes: add or update a locale.
- Existing engines do not fit: choose or extend a locale engine.
- Output differs by platform: probe globalization data and add a narrow override.
- Documentation is wrong or unclear: contribute documentation.
- You need a field name or engine contract: use the YAML reference.
Language contribution is visible here without being a prerequisite for using Humanizer. User guidance stays under Languages and cultures.
Report enough detail to reproduce the issue
A useful issue report is a compact, reproducible record:
Culture: fr-CA
Humanizer version: <version>
API call: 2.ToWords(culture)
Expected: ...
Actual: ...
Platform/TFM: macOS, net8.0
That is enough to route the problem before anyone changes locale ownership or grammar.
Reproduce before changing locale ownership
Do not start by copying a parent locale or adding a culture code to a registry. A successful lookup is not proof of natural output, and package presence is not capability coverage. Trace the owning YAML surface and reproduce the behavior first.