Tibetan Phonetics Engine
Description
The goal of this code is to provide a library to:
- implement the conversion of a Tibetan Unicode word into IPA, according to different schemes / dialects
- implement some conversions between IPA and phonetics readable by people with various language backgrounds (Chinese, English, etc.)
The primary focus of this library is litterary pronounciation, ideally representing how an umze would pronounce a traditional text, but contributions for other uses are welcome. We also do not handle Sanskrit transliteration (this can be done through custom exceptions lists).
Note that this library integrates no segmenter and needs to be applied on each word separately. You can use it in combination with pybo to get the phonetics of full sentences.
Phonetics methods
We currently provide two phonetics schemes:
Manual of Standard Tibetan (by Tournadre)
Colloquial Amdo Tibetan (by Kuo-ming Sung and Lha Byams Rgyal)
Outputs
Apart from raw IPA, we provide the following output possibilities:
Chinese phonetics
The Chinese is produced by a streamlined phonetic scheme in order to match the Mandarin phonology (vowels have been simplified and most of the Tibetan suffixes removed).
To produce the final output, we first transform the generated IPA into Zhuyin, and then the Zhuyin into Traditional Chinese characters, with a manually built correspondance list.
Installation
pip install bophono
API
To get the IPA for a word according to the MST scheme:
import bophono
# see PhonStateMST.py for other options
options = {
'aspirateLowTones': True
}
mstconverter = bophono.UnicodeToApi(schema="MST", options = options)
mstipa = mstconverter.get_api("སྐུ")
print(mstipa) # kú
Note that you must first segment your text in words and then convert each word.
Changes
See CHANGELOG.md.
License
The Python code is Copyright (C) 2018-2023 Esukhia, provided under MIT License. See CONTRIBUTORS.md for a list of authors and contributors.
Metadata
Release files for bophono 0.2.0
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 |
|---|---|---|---|---|
| bophono-0.2.0.tar.gz | 28.8 kB | Without provenance | Details for bophono-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bophono-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for bophono-0.2.0-py3-none-any.whl |
Total release size: 63.1 kB
Release files / bophono-0.2.0.tar.gz
| Download URL | bophono-0.2.0.tar.gz |
|---|---|
| Size | 28.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7871e20ef0e87c4e7561186ee99d97d091f3204d28859f940a12ba319507bb29
|
|
BLAKE2b-256 checksum How to use checksums |
d798aa3e2526e84dc59cae2641c463294e14a249976141df364bfe166e77f54d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Release files / bophono-0.2.0-py3-none-any.whl
| Download URL | bophono-0.2.0-py3-none-any.whl |
|---|---|
| Size | 34.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0a992dbf3823f6852279fc8ad9ce6d41bc783a884d48f00df1df596056e81f0d
|
|
BLAKE2b-256 checksum How to use checksums |
43acc374611303c29b76ff2981cc8c4b7830a7b58fe247194e235860ef29edb3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Security for bophono 0.2.0
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.