Skip to content

cpp-pinyin2 2.0.0

Latest

Choose a tag to compare

@wolfgitpr wolfgitpr released this 30 Oct 17:15
· 10 commits to main since this release

cpp-pinyin2 2.0.0

A rewrite rather than a release with additions: the library becomes something you instantiate, gains a C ABI,
and grows Python and C# shells on top of it. The full list of changes is CHANGELOG.md at this tag.

Install

pip install cpp-pinyin2==2.0.0
dotnet add package CppPinyin --version 2.0.0
# CMake: FetchContent with GIT_TAG v2.0.0, or build and 'cmake --install'

What is attached here

file for
cpp_pinyin2-2.0.0-py3-none-win_amd64.whl Windows x64
cpp_pinyin2-2.0.0-py3-none-manylinux_2_26_x86_64.manylinux_2_28_x86_64.whl Linux x86_64 (auditwheel-stamped)
cpp_pinyin2-2.0.0-py3-none-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl Linux aarch64 (auditwheel-stamped)
CppPinyin.nupkg .NET, ONE package carrying runtimes/ for win-x64, linux-x64 and osx-arm64

Support

  • Python >= 3.9 (the wheel is py3-none-<platform>: one artifact serves cp39 through cp313, all of which
    the suite installs and smoke-tests).
  • .NET net7.0 and net10.0.
  • C++17, via CMake, pkg-config or FetchContent.

No macOS wheel ships in 2.0.0. The macOS binary surface is built and measured on every CI run
(ci_macos_verify.sh: architecture, install name, @rpath, and an index-less install), but the release
pipeline deliberately produces no macOS wheel.

Licences

Code is Apache-2.0. The Mandarin tables are CC-CEDICT under CC BY-SA 4.0 and the Cantonese tables are
CC-Canto under CC BY-SA 3.0. Every package ships LICENSE and THIRD_PARTY_NOTICES.md, and each dialect
carries its own License.txt. The NuGet package names THIRD_PARTY_NOTICES.md as its licence file
because nuget.org will not accept an SPDX expression containing CC-BY-SA-3.0.

vcpkg

No vcpkg port is provided: this repository ships no portfile and there is no cpp-pinyin2 port in the
registry. Install from source with CMake.

A note on numbers

No accuracy figures are claimed in these notes. The corpus behind the accuracy fixtures has an unresolved
licence (recorded in docs/RELEASE_CHECKLIST.md), and the measured values live in
docs/PERFORMANCE.md and docs/DECISIONS.md ?2.1 with their dates and provenance.