RADICAL_FORMSconstant

WHAT A RADKFILE RADICAL LOOKS LIKE, AS OPPOSED TO WHAT IT IS KEYED BY.

RADKFILE predates Unicode having a character for every radical shape, so for the shapes with no character of their own it writes a whole kanji that contains the shape: 汁 for 氵, 扎 for 扌, 艾 for 艹, 込 for 辶. The stroke count beside each is the radical's, not the stand-in's (汁 sits under three strokes because 氵 is three), and every kanji listed under it is a kanji written with the shape, not with the stand-in. Drawn as written, a picker files a five-stroke kanji under three strokes and names it "soup".

So the key stays the key, since it is what the index and everything that looks a radical up speak, and anything that DRAWS a radical asks radicalForm for its shape first. This table is the package's own. Each shape is the CJK Unified Ideograph that is that shape, which nearly every font draws (EDRDG's own list of the same characters, in the CJK Radicals Supplement and Kangxi blocks, is in RADKFILE.unicode from @johnmorrisdotca/bushu/radkfile, and a test holds the two to the same set of keys).

Both 邦 and 阡 come out as 阝, which is right: it is the same shape on the right of 部 and on the left of 陸, and RADKFILE keeps two keys because the two kanji lists differ. The name tells them apart (おおざと and こざとへん).

import { RADICAL_FORMS } from "@johnmorrisdotca/bushu";

const RADICAL_FORMS: Readonly<Record<string, string>> = {
    化: "亻",
    个: "𠆢",
    并: "丷",
    刈: "刂",
    ハ: "八",
    込: "辶",
    汁: "氵",
    尚: "⺌",
    犯: "犭",
    邦: "阝",
    阡: "阝",
    忙: "忄",
    扎: "扌",
    艾: "艹",
    ヨ: "彐",
    礼: "礻",
    老: "耂",
    杰: "灬",
    初: "衤",
    買: "罒",
    疔: "疒",
    禹: "禸",
    滴: "啇",
    "｜": "丨",
    ノ: "丿",
}

import { RADICAL_FORMS } from "@johnmorrisdotca/bushu";

console.log(RADICAL_FORMS["汁"]);

氵