Announcing Humanizer 2.0

Earlier today we finalized and published the next major release of Humanizer. This version includes many fixes and new features, many of them coming directly from the community. A huge thank you to all those who have contributed!

You can find the latest Humanizer on NuGet and the website contains the latest documentation. The release notes contains the full details of the changes.

I wanted to call out a few things though:

  • The Humanizer package now supports selecting locales to install. This was done by using a little-known feature of NuGet called satellite packages. The main Humanizer package is now a meta-package that pulls in all language packages plus the core library; this is the existing behavior of Humanizer today.
    • To install English only, you may elect to install Humanizer.Core directly
    • To install specific a language or set of languages, you can specify Humanizer.Core.<locale> where <locale> represents a supported language package.
  • There is currently a known issue with DNX with satellite packages. It might affect CLI too; track that one here.
  • For best results, using project.json/NuGet v3 is highly recommended over packages.config/NuGet v2. The key difference is that all of the child packages are transitively included instead of directly referenced in your packages.config file. project.json is supported in any project type, not just .NET Core or UWP projects.

Finally, I wanted to thank Mehdi Khalili for trusting me with the stewardship of the project. Mehdi did a fantastic job building Humanizer up and getting the community involved to contribute back. I also would like to thank Alexander I. Zaytsev and Max Malook for their efforts in coordinating the community contributions and guide the project forward.