comments: src/languages/g* complete — galician through gujarati, all 22 files - #699
Merged
Conversation
…22 files
926 → 823 comment lines. Comments only; all verified code-identical to
main. The biggest headers in the letter took the biggest cuts:
gujarati/normalize 228 → 204 greek/normalize 282 → 259
guarani/numbers 100 → 56 german/* 210 → 197
No defects in the source. One I INTRODUCED and caught: slicing
guarani/numbers.ts's header left a duplicate ` */`, which is a syntax
error. The emit check flagged it — that is the third time this session
the mechanical edit was the defect, after `авторed` in abkhaz and the
half-replaced ★⚠ in cherokee/chuvash.
Kept, and g* has two cases where the ARGUMENT is the value rather than
the fact:
guarani/numbers.ts 100 lines cut to 56, but the CASE survives intact,
because without it someone will "fix" the academic
neologisms to the Spanish loans everyone actually
speaks. Both halves kept: that Estigarribia calls
the system "purely of academic use", AND that the
Spanish route cannot be taken without inventing
data — there is no attested Guaraní spelling of a
Spanish numeral, because written Guaraní sidesteps
the question with arabic digits. Plus the fact
that stops it reading as dead: 6–12 are lexicalised
in the month names (jasypokõi July), so a speaker
who says *siete* still says jasypokõi.
gujarati/normalize inheriting Hindi's symbol words is a SILENT
DELETION, not a wrong reading — they are written in
Devanagari, which is not in GUJARATI_WORD, so the
tokenizer never emits them. "45%" → [pˈistalis].
Also kept: german's ordinal detector, which fires on the FOLLOWING word
or a licensing article precisely so a sentence-final `N.` matches
neither; and greek's `\b` warning plus its Latin↔Greek homoglyph class,
where a Latin `o` typed for the article ο makes the word vanish.
Notation: 3 inventory-boilerplate copies, 5 ★ → ⚠, gan's 🔷 spelled out.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012Lc3WnUgogC7okV7n53vjr
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
galician, gan, georgian, german, greek, guarani, gujarati — in directory order, nothing skipped. 926 → 823 comment lines. Comments only; all verified code-identical to
main.greek/normalize.tsgujarati/normalize.tsgerman/*guarani/numbers.tsNo defects in the source — one I introduced
Slicing
guarani/numbers.ts's header left a duplicate*/, which is a syntax error. The emit check caught it before push.That's the third time this session the mechanical edit was itself the defect — after
авторedin abkhaz and the half-replaced★⚠in cherokee/chuvash. Worth stating plainly: bulk comment rewriting has a defect rate of its own, and code-identity verification on every batch is what keeps it from shipping.Where the argument is the value, not the fact
guarani/numbers.ts— cut 100 → 56, but the case survives intact. Without it, someone will "fix" the academic neologisms to the Spanish loans everyone actually speaks. Both halves kept:Plus the fact that stops it reading as dead: 6–12 are lexicalised in the month names, so a speaker who says siete for 7 still says jasypokõi for July.
gujarati/normalize.ts— inheriting Hindi's symbol words is a silent deletion, not a wrong reading. They're written in Devanagari, which isn't inGUJARATI_WORD, so the tokenizer never emits them at all:"45%"→[pˈistalis]. That reframing is the whole reason the file exists, and it was buried under a defect inventory.Also kept
N.matches neither; and the two-form declension (am/im/des→ weak -en,das/der/die→ -e)\bwarning, and the Latin↔Greek homoglyph class where a Latinotyped for the article ο makes the word vanish into the foreign pathNotation
3 inventory-boilerplate copies, 5
★→⚠, gan's🔷spelled out.Checks
npm run typecheckclean🤖 Generated with Claude Code
https://claude.ai/code/session_012Lc3WnUgogC7okV7n53vjr