Skip to content

comments: src/languages/k* complete — kabuverdianu through kyrgyz, all 47 files - #703

Merged
christopherthompson81 merged 1 commit into
mainfrom
comment-sweep-k
Aug 7, 2026
Merged

comments: src/languages/k* complete — kabuverdianu through kyrgyz, all 47 files#703
christopherthompson81 merged 1 commit into
mainfrom
comment-sweep-k

Conversation

@christopherthompson81

Copy link
Copy Markdown
Owner

kabuverdianu, kalaallisut, kamba, kannada, karakalpak, kazakh, khmer, kiche, kikuyu, kinyarwanda, kirundi, korean, kurmanji, kyrgyz — in directory order, nothing skipped. 1000 → 961 on the files that changed. Comments only; all verified code-identical to main.

One defect — collateral damage from an earlier automated pass

kazakh/normalize.ts's opening sentence was garbled with an unclosed parenthesis:

Kazakh's DEFINING rule (measured over the kk_hr FLEURS corpus — * CASE SUFFIX after a digit, exactly as trap 14 (agreement cannot be applied to digits) predicted:

An inline gloss had been spliced into the middle of a sentence and swallowed its close. The rule it describes was intact underneath; it now states itself without the scaffolding.

Four more inline trap glosses cleared from kazakh and khmer — the last in the fleet outside n–z.

Kept

kazakh — the suffix must agree by vowel harmony, so gluing the written suffix to the digits is wrong: 200-ге is екі жүзге, with the -ге on жүз. The written suffix gives you the CASE; the WORD supplies the ending.

korean — the number–counter boundary is where the sandhi lives: 17일 is [ɕip̚t͡ɕʰiɾiɭ] because ㄹ resyllabifies into 일, and splitting the token loses it entirely. And which numeral series a counter takes is a property of the counter3명 is 세 명, not 삼 명 — with 개 guarded against 개월/개국, which are Sino.

khmer — probe the unit, not the digit: ការេ is 0/0 digit-adjacent and looks unsourceable, but ² attaches to a unit and ការេ is exactly the square-metre word.

Notation

7 inventory-boilerplate copies, 15 , kiche's and karakalpak's 🔷 spelled out.

Checks

  • npm run typecheck clean
  • 224 test files / 3114 tests passing

🤖 Generated with Claude Code

https://claude.ai/code/session_012Lc3WnUgogC7okV7n53vjr

…l 47 files

1000 → 961 on the files that changed. Comments only; all verified
code-identical to main.

One defect, and it is damage from the earlier trap-reference expansion
rather than original prose:

  kazakh/normalize.ts  the header's opening sentence was garbled with an
    unclosed parenthesis — "measured over the kk_hr FLEURS corpus — *
    CASE SUFFIX after a digit, exactly as trap 14 (agreement cannot be
    applied to digits) predicted:" — where an inline gloss had been
    spliced into the middle of a sentence and swallowed its close. The
    rule it describes is intact and now states itself.

Four more of those inline trap glosses cleared from kazakh and khmer,
the last in the fleet outside n–z.

Kept, per language:
  kazakh  the suffix must AGREE by vowel harmony, so gluing the WRITTEN
          suffix to the digits is wrong — `200-ге` is *екі жүзге*, with
          the -ге on жүз. The written suffix gives the CASE; the WORD
          supplies the ending.
  korean  the number–counter boundary is where the SANDHI lives: 17일 is
          [ɕip̚t͡ɕʰiɾiɭ] because ㄹ resyllabifies, and splitting the token
          loses it. And which numeral series a counter takes is a
          property of the COUNTER — 3명 is 세 명, not 삼 명 — with 개
          guarded against 개월/개국, which are Sino.
  khmer   probe the UNIT, not the digit: ការេ is 0/0 digit-adjacent and
          looks unsourceable, but `²` attaches to a unit and ការេ is
          exactly the square-metre word.

Notation: 7 inventory-boilerplate copies, 15 ★ → ⚠, kiche's and
karakalpak's 🔷 spelled out.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012Lc3WnUgogC7okV7n53vjr
@christopherthompson81
christopherthompson81 merged commit 8dc963a into main Aug 7, 2026
@christopherthompson81
christopherthompson81 deleted the comment-sweep-k branch August 7, 2026 03:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant