fix(i18n): make the Korean locale actually work end to end

Registering `ko` in the `Locale` union left seven locale-keyed tables
without an entry, so the build could not type-check and the safety
screens, the citation-coverage grader and the reference-range parser
read nothing at all for a Korean reader.

Three failures were not missing keys but wrong assumptions:

- The shared fold decomposes with NFD and strips U+0300-U+036F. Latin
  accents become plain letters, but Hangul decomposes into jamo, which
  are not in that range and survived — so folded Korean text was a jamo
  sequence no precomposed table entry could ever match. It recomposes to
  NFC now; every Latin, Polish and German fold is byte-identical.
- `normaliseLabKey` kept `[a-z0-9]`, which reduced every Korean analyte
  name to the empty string, so the derived index held none of them and a
  Korean cholesterol result reached a FHIR export uncoded.
- The reference-range parser had the hyphen and the dashes but not the
  tilde a Korean lab actually prints (`3.5~5.0`).

The Korean safety banks carry no `\b` next to a Hangul token — `\b` is
an ASCII `\w` boundary and Hangul is not `\w`, so `/\b증량/` matches
nothing — and the clause order is the mirror of the Latin banks, since
Korean closes with the verb. The dose patterns require a target-marking
particle for the same reason the Latin banks require "to"/"by": without
it the permitted restatement "7.5mg을 복용 중이고, 체중은 내려가고
있어요" tripped the lowering pattern.

The Coach and Insights prompts route `ko` down the reviewed English body
plus a Korean reply directive; there is no `safety-contracts.ko.yaml`, so
the native builder has no Korean ground rules to compose from.
This commit is contained in:
aucun6352 committed 2026-08-26 20:00:44 +09:00
1 parent f1b0420479
commit f7cc47850a
29 files changed
+207 -18

No files matched your search

+13 -1
View File
@@ -259,6 +259,15 @@ export const RANGE_PROSE: Record<Locale, RangeProse> = {
"wartosci referencyjne",
"normy laboratoryjne",
],
}, // Korean marks a bound with a POSTPOSITION — "5.0 이하", "3.5 이상" — and the
// matchers here are prefix-anchored, so only the prefix-shaped notation is
// listed. A postfixed Korean range still falls through to text-only, which
// `isUnreadableRange` reports rather than hides.
ko: {
twoSided: ["에서", "부터"],
upper: ["최대", "최고"],
lower: ["최소", "최저"],
filler: ["참고치", "참고범위", "정상치", "정상범위", "기준치", "기준범위"],
},
};
@@ -291,7 +300,10 @@ function proseAlternation(field: keyof RangeProse): string {
* "e" and "y" are one letter long, and a bare `e` that could sit between two
* digits would read "3.5e5" as a window.
*/
const SYMBOL_SEP = String.raw`-|–|—|‒|…|\.{2,3}`;
// U+007E and the fullwidth U+FF5E are the separator a Korean lab prints
// ("3.5~5.0"); both are added here rather than to `twoSided` because they are
// symbols, and the symbol branch needs no surrounding whitespace.
const SYMBOL_SEP = String.raw`-|–|—|‒|~|~|…|\.{2,3}`;
/** Prefixes that state a ceiling only. */
const UPPER_PREFIX = `(?:<=|<|≤|${proseAlternation("upper")})`;