Convert Korean people’s Hangul names to romanized versions
Korean script (Hangul) has used various notations over the years to be
converted to latin (Roman) characters. The currently used official system for
normal words is Revised Romanization (RR), which eliminated ambiguity in
the old system McCune–Reischauer (McR). McR uses accented characters to
denote differences in pronounciation. Accented characters were commonly not used
in internet communications as they are hard to type and/or not well supported in
fonts. Over the years font support has improved tremendously, but keyboard
support is still flunky.
The lack of accents caused ambiguity in romanized words and people had to guess from the context what the writer meant (yo and yŏ were both spelled as yo). The Revised Romanization system uses plain characters from the ASCII range to denote the differences in pronounciation for example through the use of multi-letter vowels (yeo instead of yŏ).
However, for people’s names (famous or not), the rules are bent, because people are used to a certain romanization of their name and have traditionally not strictly adhered to one system or another. The classical example is that the surname 김 is always romanized to Kim, whereas RR dictates Gim.
This library contains a set of rules that can be implemented to deviate from RR notation using transliteration definitions and succession rules. It was inspired by the author’s work on Dramawiki, which uses a documented set of prefences, so that people with the same name in Hangul script, end up romanized exactly the same. Since Dramawiki aims to support English readers it didn’t make sense to create pages with titles written in Hangul.
Metadata
Release files for hangul-names 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 |
|---|---|---|---|---|
| hangul-names-0.4.2.tar.gz | 9.6 kB | Without provenance | Details for hangul-names-0.4.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| hangul_names-0.4.2-py3-none-any.whl | Python 3 | none | any | Details for hangul_names-0.4.2-py3-none-any.whl |
Total release size: 18.8 kB
Release files / hangul-names-0.4.2.tar.gz
| Download URL | hangul-names-0.4.2.tar.gz |
|---|---|
| Size | 9.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dfcd3d10d60b991dff369f0048926603eb5f6ec00612961050d5abcc359626a9
|
|
BLAKE2b-256 checksum How to use checksums |
94c73ddf9dd956c715287d315efe0c5179a380dc2b3ec102e2c234285c5be02d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/49.2.0 requests-toolbelt/0.9.1 tqdm/4.48.0 CPython/3.8.5
|
Release files / hangul_names-0.4.2-py3-none-any.whl
| Download URL | hangul_names-0.4.2-py3-none-any.whl |
|---|---|
| Size | 9.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f9588eeb9b52c252fdf9a9a3ca46feb6951d1f5420a6bd0220f488c64f57d060
|
|
BLAKE2b-256 checksum How to use checksums |
6b8e0f40356a6e4c5259b39c4b74b54e315d48978bc0a79515ef13f3b12564dd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/49.2.0 requests-toolbelt/0.9.1 tqdm/4.48.0 CPython/3.8.5
|
Security for hangul-names 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.