Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

opencc-data JSDelivr badge

繁體中文

A collection of dictionary data, configs, and test data for Simplified and Traditional Chinese conversions from the OpenCC project.

Compatibility

This package is intended for opencc-js and other OpenCC-compatible implementations that consume OpenCC dictionary and config data.

  • Strict Version Matching: Compatibility is only guaranteed when the version of opencc-data strictly matches the version of the consumer package.
  • Breaking Changes: We do not guarantee compatibility between different versions of opencc-data. Structure or file names may change to align with upstream OpenCC updates.

Data Sync Policy

This package syncs dictionary .txt files and config .json files from OpenCC's generated resource zip, plus test/testcases/testcases.json from the upstream repository. Each sync keeps the upstream resource manifest as an internal baseline so future updates can detect substantive data changes by resource hash.

Usage

Use the config files shipped in data/config/ as the source of truth for dictionary order and conversion-chain behavior. Config contents can change between OpenCC versions, so consumers should load the matching config file for the package version they depend on instead of hard-coding dictionary lists from this README.

Dictionary text files are shipped in data/. Config files reference those dictionaries by file name and preserve OpenCC's stage/group ordering semantics.

Python consumers can install the opencc-data package from PyPI and use the opencc_data module to locate packaged resources:

import opencc_data

config_file = opencc_data.config_path("s2t.json")
dictionary_file = opencc_data.data_path("STCharacters.txt")
testcases_file = opencc_data.test_data_path("testcases.json")

Release versions match across npm and PyPI, such as 1.3.2. For next prereleases, PyPI uses the PEP 440 equivalent of the npm version: 1.3.2-next.20260628 is published to PyPI as 1.3.2.dev20260628.

Metadata

Release files for opencc-data 1.3.2.dev20260628

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for opencc-data 1.3.2.dev20260628
File Size Uploaded
opencc_data-1.3.2.dev20260628.tar.gz 531.1 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for opencc-data 1.3.2.dev20260628
File Interpreter ABI Platform
opencc_data-1.3.2.dev20260628-py3-none-any.whl Python 3 none any Details

Total release size: 1.1 MB

Release files / opencc_data-1.3.2.dev20260628.tar.gz

Download URL opencc_data-1.3.2.dev20260628.tar.gz
Size 531.1 kB
Tags Source
SHA-256 checksum
How to use checksums
95864e84d4c0958a6113bb380c4fef12dbc2f0ddcf231a752a0daea28731711f
BLAKE2b-256 checksum
How to use checksums
768219af97c26182aaa81d29e233851a97caa36401e9ee3d428d1ea8a7043f75
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jun 28, 2026.

Transparency log

Release files / opencc_data-1.3.2.dev20260628-py3-none-any.whl

Download URL opencc_data-1.3.2.dev20260628-py3-none-any.whl
Size 541.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d9b1111210997ceb52ca691d20ce356e0f5ce4008ac99703b9d33a6790c1dca2
BLAKE2b-256 checksum
How to use checksums
5349908c1f7573f6bd15efd13f9702e3973fc90316af792e8758d622a77a0cb1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jun 28, 2026.

Transparency log
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page