Commit History
-
[NOTICKET] refactor(knowledge-parsing): English throughout the module
The parsing half was written in Indonesian — identifiers, docstrings, comments, manifest keys and console output. Everything else in the repo is English, and this module is the newest work, so it is the one to bring into line rather than the older code around it. Renamed across the module: parse_dokumen -> parse_document, normalisasi -> normalise, pulihkan_batas_kata -> restore_word_boundaries, kosakata_layak -> trustworthy_vocabulary, periksa_items -> check_items, CatatanDokumen -> DocumentRecord, and the locals with them. Docstrings and comments were REWRITTEN rather than translated word for word. Several carry the reasoning behind a decision — why `\frac` is unwrapped before the braced wrappers, why a heading never enters `text`, why the digit threshold is 3 — and a mechanical translation would have flattened exactly the part worth keeping. Manifest keys move too: detik_per_halaman -> seconds_per_page, peringatan -> warnings, jenis -> kind, galat -> error. That is a data change, …7f153d6
-
[NOTICKET] feat(knowledge-parsing): one runner, in Python rather than shell
Running the pipeline meant six environment variables and an interpreter path from another repo, typed out every time. This wraps it: py scripts/parse.py # Windows python3 scripts/parse.py # Linux Python, not shell, and that was learned the hard way. A bash version and a PowerShell version were both written first, and between them hit two traps in twenty minutes: - CRLF. core.autocrlf=true rewrites .sh on Windows checkout, and bash then dies on line one with `set: pipefail` — a message that names nothing. - A trailing backslash. The default input path contains spaces, so PowerShell quotes it, the final backslash escapes the closing quote, and the NEXT argument is swallowed: `--backend pipeline` ended up inside `--input`. `subprocess` takes an argument list and never goes through a shell, so neither is possible here. One file instead of two, and readable by anyone on the team without knowing both shells. The backend is chosen from…74acbf7