voxnorm 0.1.0__tar.gz

voxnorm-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,21 @@
+name: ci
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.10", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+      - run: uv python install ${{ matrix.python-version }}
+      - run: uv sync --python ${{ matrix.python-version }}
+      - run: uv run ruff check .
+      - run: uv run ruff format --check .
+      - run: uv run pytest -q

voxnorm-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,34 @@
+# Publishes to PyPI on a version tag (v0.1.0, v0.2.0, ...) via PyPI trusted
+# publishing — configure the publisher once on pypi.org (project: voxnorm,
+# owner: allen2c, repo: voxnorm, workflow: release.yml, environment: pypi)
+# and no API token ever lives in this repo.
+name: release
+
+on:
+  push:
+    tags: ["v*"]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+      - run: uv build
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1

voxnorm-0.1.0/.gitignore

@@ -0,0 +1,218 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#   that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#   you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml

voxnorm-0.1.0/CHANGELOG.md

@@ -0,0 +1,19 @@
+# Changelog
+
+## 0.1.0
+
+First release.
+
+- Language-neutral token scanner: clock times, ISO dates, phone numbers,
+  currency amounts (NT$/US$/USD/NTD/$/€/¥/₩/£), percentages, room/extension
+  codes, decimals, comma-grouped and bare integers.
+- Verbalisers for Traditional Chinese (zh-TW, spelled out in-repo with the
+  兩/二 reading rules), Simplified Chinese (zh-CN, a re-spelling of the same
+  readings with 万亿 for 10^12 and ¥ as renminbi), English, Japanese, and
+  Korean (native-numeral hours, irregular months) — the latter three on
+  num2words.
+- Script-based language auto-detection (kana → ja, hangul → ko, Han → zh
+  with a distinctive-glyph Simplified check, else en) and an explicit `lang`
+  hint that always wins (`zh-CN`/`zh-Hans`/`zh-SG` select Simplified).
+- Charter: structural only, never guess — ambiguous forms (every slash form,
+  invalid clock strings, colon-adjacent digits) stay written.

voxnorm-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

voxnorm-0.1.0/PKG-INFO

@@ -0,0 +1,105 @@
+Metadata-Version: 2.5
+Name: voxnorm
+Version: 0.1.0
+Summary: Text normalization for TTS: written forms into spoken forms, multilingual, pure Python
+Project-URL: Repository, https://github.com/allen2c/voxnorm
+Author: Allen Chou
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: speech,spoken-form,text-normalization,tts,verbalization,zh-tw
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Multimedia :: Sound/Audio :: Speech
+Classifier: Topic :: Text Processing :: Linguistic
+Requires-Python: >=3.10
+Requires-Dist: num2words>=0.5.14
+Description-Content-Type: text/markdown
+
+# voxnorm
+
+Text normalization for TTS: written forms into spoken forms, multilingual,
+pure Python. Currently speaks **Traditional Chinese (zh-TW),
+Simplified Chinese (zh-CN), English, Japanese, and Korean**.
+
+Language models and databases write for the eye — `12:00`, `NT$1,200`,
+`0912-345-678` — and a small TTS frontend handed that text verbatim has to
+guess, and guesses badly. voxnorm rewrites the written forms into what a
+speaker would actually say, and leaves everything else character-for-character
+alone:
+
+```python
+>>> import voxnorm
+>>> voxnorm.normalize("會議在12:00開始")
+'會議在十二點開始'
+>>> voxnorm.normalize("The meeting starts at 12:00")
+"The meeting starts at twelve o'clock"
+>>> voxnorm.normalize("会議は12:00からです")      # kana → Japanese
+'会議は十二時からです'
+>>> voxnorm.normalize("회의는 12:00에 시작합니다")  # hangul → Korean (native-numeral hours)
+'회의는 열두 시에 시작합니다'
+>>> voxnorm.normalize("電話是0912-345-678。")
+'電話是零九一二三四五六七八。'
+>>> voxnorm.normalize("NT$1,200", lang="zh")
+'新台幣一千兩百元'
+>>> voxnorm.normalize("会议在12:00开始")        # simplified glyphs → zh-CN
+'会议在十二点开始'
+```
+
+## Design
+
+Two layers, split where languages stop sharing:
+
+- **Detection is language-neutral** (`voxnorm/tokens.py`): one scanner finds
+  the spans — times, ISO dates, phone numbers, currency, percentages, room
+  numbers, decimals, integers — and names their kind.
+- **Verbalisation is per-language** (`voxnorm/zh.py`, `cn.py`, `en.py`,
+  `ja.py`, `ko.py`): a new language is a new module and one registry entry. English,
+  Japanese and Korean ride on
+  [num2words](https://pypi.org/project/num2words/) for their number words,
+  each adding the readings the library cannot know — a Japanese year without
+  the era default, Korean native-numeral hours (한 시, never 일 시), the
+  irregular Korean months 유월/시월. Chinese is spelled out in-repo,
+  Traditional first, because the 兩/二 reading choice (一千兩百, never
+  一千二百 in zh-TW speech) is exactly what general-purpose converters get
+  wrong; the Simplified variant re-spells that one output vocabulary
+  (`兆` → `万亿`, and `¥` reads as renminbi rather than yen).
+
+Language is decided per call: an explicit hint wins
+(`normalize(text, lang="zh-TW")`), otherwise script evidence decides — kana
+means Japanese, hangul Korean, a Han character Chinese (Simplified when
+distinctive simplified glyphs appear, Traditional otherwise), else English. (A
+Japanese sentence written entirely in kanji is script-identical to Chinese
+and lands on the Chinese reading — pass `lang="ja"` when you know better.)
+
+The charter is **structural only, never guess**: a form whose reading is
+ambiguous does not convert (`1/2` the fraction and `8/17` the date are the
+same slash string, so no slash form converts at all). What is not converted is
+simply spoken as written — which is where it started.
+
+## Why not an FST toolkit
+
+nemo_text_processing and WeTextProcessing were measured before this package
+was written. Both depend on pynini, which publishes no aarch64 wheel — on an
+ARM box they need OpenFst compiled from source and a permanently vendored
+`libfst.so` — and both mis-read the very classes this package exists for:
+phone numbers as quantities, `302號房` as a date, and (WeTextProcessing)
+force-simplifying every Traditional character in the sentence it touches. The
+classes a spoken product needs are a bounded set; implementing them directly
+costs ~3 MB of pure Python and stays debuggable.
+
+## Install
+
+```sh
+uv add voxnorm      # or: pip install voxnorm
+```
+
+## Development
+
+```sh
+uv sync
+uv run pytest
+uv run ruff check .
+```
+
+Apache-2.0.

voxnorm-0.1.0/README.md

@@ -0,0 +1,87 @@
+# voxnorm
+
+Text normalization for TTS: written forms into spoken forms, multilingual,
+pure Python. Currently speaks **Traditional Chinese (zh-TW),
+Simplified Chinese (zh-CN), English, Japanese, and Korean**.
+
+Language models and databases write for the eye — `12:00`, `NT$1,200`,
+`0912-345-678` — and a small TTS frontend handed that text verbatim has to
+guess, and guesses badly. voxnorm rewrites the written forms into what a
+speaker would actually say, and leaves everything else character-for-character
+alone:
+
+```python
+>>> import voxnorm
+>>> voxnorm.normalize("會議在12:00開始")
+'會議在十二點開始'
+>>> voxnorm.normalize("The meeting starts at 12:00")
+"The meeting starts at twelve o'clock"
+>>> voxnorm.normalize("会議は12:00からです")      # kana → Japanese
+'会議は十二時からです'
+>>> voxnorm.normalize("회의는 12:00에 시작합니다")  # hangul → Korean (native-numeral hours)
+'회의는 열두 시에 시작합니다'
+>>> voxnorm.normalize("電話是0912-345-678。")
+'電話是零九一二三四五六七八。'
+>>> voxnorm.normalize("NT$1,200", lang="zh")
+'新台幣一千兩百元'
+>>> voxnorm.normalize("会议在12:00开始")        # simplified glyphs → zh-CN
+'会议在十二点开始'
+```
+
+## Design
+
+Two layers, split where languages stop sharing:
+
+- **Detection is language-neutral** (`voxnorm/tokens.py`): one scanner finds
+  the spans — times, ISO dates, phone numbers, currency, percentages, room
+  numbers, decimals, integers — and names their kind.
+- **Verbalisation is per-language** (`voxnorm/zh.py`, `cn.py`, `en.py`,
+  `ja.py`, `ko.py`): a new language is a new module and one registry entry. English,
+  Japanese and Korean ride on
+  [num2words](https://pypi.org/project/num2words/) for their number words,
+  each adding the readings the library cannot know — a Japanese year without
+  the era default, Korean native-numeral hours (한 시, never 일 시), the
+  irregular Korean months 유월/시월. Chinese is spelled out in-repo,
+  Traditional first, because the 兩/二 reading choice (一千兩百, never
+  一千二百 in zh-TW speech) is exactly what general-purpose converters get
+  wrong; the Simplified variant re-spells that one output vocabulary
+  (`兆` → `万亿`, and `¥` reads as renminbi rather than yen).
+
+Language is decided per call: an explicit hint wins
+(`normalize(text, lang="zh-TW")`), otherwise script evidence decides — kana
+means Japanese, hangul Korean, a Han character Chinese (Simplified when
+distinctive simplified glyphs appear, Traditional otherwise), else English. (A
+Japanese sentence written entirely in kanji is script-identical to Chinese
+and lands on the Chinese reading — pass `lang="ja"` when you know better.)
+
+The charter is **structural only, never guess**: a form whose reading is
+ambiguous does not convert (`1/2` the fraction and `8/17` the date are the
+same slash string, so no slash form converts at all). What is not converted is
+simply spoken as written — which is where it started.
+
+## Why not an FST toolkit
+
+nemo_text_processing and WeTextProcessing were measured before this package
+was written. Both depend on pynini, which publishes no aarch64 wheel — on an
+ARM box they need OpenFst compiled from source and a permanently vendored
+`libfst.so` — and both mis-read the very classes this package exists for:
+phone numbers as quantities, `302號房` as a date, and (WeTextProcessing)
+force-simplifying every Traditional character in the sentence it touches. The
+classes a spoken product needs are a bounded set; implementing them directly
+costs ~3 MB of pure Python and stays debuggable.
+
+## Install
+
+```sh
+uv add voxnorm      # or: pip install voxnorm
+```
+
+## Development
+
+```sh
+uv sync
+uv run pytest
+uv run ruff check .
+```
+
+Apache-2.0.