cihaidata-unihan - tool to build unihan into simple data format CSV format. Part of the cihai project.
Unihan’s data is disperved across multiple files in the format of:
U+3400 kCantonese jau1 U+3400 kDefinition (same as U+4E18 丘) hillock or mound U+3400 kMandarin qiū U+3401 kCantonese tim2 U+3401 kDefinition to lick; to taste, a mat, bamboo bark U+3401 kHanyuPinyin 10019.020:tiàn U+3401 kMandarin tiàn
cihaidata_unihan/process.py will download Unihan.zip and build all files into a single tabular CSV (default output: ./data/unihan.csv):
char,ucn,kCantonese,kDefinition,kHanyuPinyin,kMandarin 丘,U+3400,jau1,(same as U+4E18 丘) hillock or mound,,qiū 㐁,U+3401,tim2,"to lock; to taste, a mat, bamboo bark",10019.020:"tiàn,tiàn"
process.py supports command line arguments. See cihaidata_unihan/process.py CLI arguments for information on how you can specify custom columns, files, download URL’s and output destinations.
Being built against unit tests. See the Travis Builds and Revision History.
Usage
To download and build your own unihan.csv:
$ ./cihaidata_unihan/process.pyCreates data/unihan.csv.
See cihaidata_unihan/process.py CLI arguments for advanced usage examples.
Structure
# dataset metadata, schema information.
datapackage.json
# (future) when this package is stable, unihan.csv will be provided
data/unihan.csv
# stores downloaded Unihan.zip and it's txt file contents (.gitignore'd)
data/build_files/
# script to download + build a SDF csv of unihan.
cihaidata_unihan/process.py
# unit tests to verify behavior / consistency of builder
tests/*
# python 2/3 compatibility modules
cihaidata_unihan/_compat.py
cihaidata_unihan/unicodecsv.py
# python module, public-facing python API.
__init__.py
cihaidata_unihan/__init__.py
# utility / helper functions
cihaidata_unihan/util.pyCihai is not required for:
data/unihan.csv - simple data format compatible csv file.
cihaidata_unihan/process.py - create a data/unihan.csv.
When this module is stable, data/unihan.csv will have prepared releases, without requires using cihaidata_unihan/process.py. process.py will not require external libraries.
Examples
Related links:
CSV Simple Data Format (SDF): http://data.okfn.org/standards/simple-data-format
Tools: http://data.okfn.org/tools
Python support |
Python 2.7, >= 3.3, pypy/pypy3 |
Source |
|
Docs |
|
Changelog |
https://cihaidata-unihan.git-pull.com/en/latest/history.html |
API |
|
Issues |
|
Travis |
|
Test coverage |
|
pypi |
|
OpenHub |
|
License |
MIT. |
git repo |
|
install dev |
|
tests |
|
1 maintainer
Metadata
1 maintainer
Release files for cihaidata-unihan 0.4.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cihaidata-unihan-0.4.2.tar.gz | 11.7 kB | Without provenance | Details for cihaidata-unihan-0.4.2.tar.gz |
Release files / cihaidata-unihan-0.4.2.tar.gz
| Download URL | cihaidata-unihan-0.4.2.tar.gz |
|---|---|
| Size | 11.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f513cde270acdb165087ffc673aab857f498acb174bb28cfcc9f82b9f3cb5d5e
|
|
BLAKE2b-256 checksum How to use checksums |
d4e60534af69077b5ebf3e8ab2f8a383263ce42e72267388592735d7139b4d74
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for cihaidata-unihan 0.4.2
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
