How openstack-kr/knu_i18n_2025 works
Project type and purpose
• This is a CLI-based internationalization (i18n) pipeline/toolset written in Python and Bash.
• Its goal is to generate and validate translated “.po” files from template “.pot” files, apply glossary rules, and ensure quality via automated checks (PEP8, ansible, custom validators).
File structure
• Top-level scripts and orchestration:
• main.sh – entry point that sequences the pipeline.
• translate.py – core translation logic (reads templates, applies glossary, writes .po).
• utils.py – shared helper functions (file I/O, formatting).
• requirements.txt, tox.ini – dependency and code-quality tooling.
• Data directories:
• glossary/ – JSON and PO glossary entries for term consistency.
• pot/ – master “.pot” templates (e.g., releasenotes_swift.pot, sample.pot).
• po/ – generated and sample translation directories (organized by model and locale).
• Validation:
• validate/ – custom translation validators (check.py) plus sample .po files and bad_translations.txt as test cases.
• Configuration:
• experiments.json – optional config for experimental settings.
• Build & QA:
• tox integration for PEP8 and ansible playbook checks.
README for additional insights
• High-level usage: pip install, then bash main.sh.
• Quality gates: tox -e pep8 and tox -e ansible.
Detail level
• Sub-components where relevant (e.g., utils.py under Translation Engine)
• Call out configuration points (requirements.txt, experiments.json)
• Parallel flows if multiple locales or models are processed concurrently