prosolis
ccb43e5a4d
The plan said "Hunspell pt-PT vendored like en-US". Measuring that first is what saved it: nspell expands affixes eagerly on construction, and European Portuguese's 1,340 rules over 44,257 stems want over a gigabyte of browser heap — ~340 MB for the first 12,000 entries, and no return at all after three minutes on the whole file. So the expansion runs once at build time instead: 1,039,058 forms, 2.66 MB gzipped, read by the same nspell in 842 ms. The obvious npm package would also have shipped the wrong language. Both dictionary-pt and dictionary-pt-br carry VERO, the Brazilian word list, so vendoring by name puts pt-BR spellings behind a pt-PT label — the drift SUGGESTIONS §3 warns about, arriving through the packaging where no reviewer can see it. The source is Projecto Natura's, and the build script now asserts the fault lines (receção in, recepção out) before writing anything. Spellcheck consults both dictionaries and flags only what both reject, which is the no-detector answer to a pair with no script boundary. The word card does the same in the other direction: "data" is a word in both languages, so Petal shows both readings rather than guessing which she meant. Writing the tests caught the one real bug — extendedAlphabet was a snapshot while correct/suggest read live, and her dictionary arrives after English, so every lookup would have resolved "cora" while the underlines were already right. Not done, and not claimed: the pack has not been read by a pt-PT speaker, and the Piper voice is deferred with the deploy. Claude-Session: https://claude.ai/code/session_016y6gyuHkQXPiEuW8RGQyua
46 lines
1.7 KiB
TypeScript
46 lines
1.7 KiB
TypeScript
// GlossTip is the inline hover gloss: rest the pointer on an English word and a
|
|
// small bubble shows its Chinese meaning, pulled instantly from the offline
|
|
// gloss dataset. It's a pure reading aid — pointer-events are off so it never
|
|
// steals hover or blocks a click, and it sits just under the word. Bilingual
|
|
// chrome elsewhere puts zh first; here the gloss IS the content (the word is
|
|
// already on screen), so the bubble shows only the 中文.
|
|
|
|
interface Props {
|
|
gloss: string
|
|
// The English meaning of the same token read as a word of the writer's own
|
|
// language, when it is one. On a Latin-script pair "sale" is both, and the
|
|
// bubble shows the two readings stacked rather than picking one — the same
|
|
// both-directions rule the word card follows, in one line less space.
|
|
reverse?: string
|
|
// How the writer's language names itself, to label the second line.
|
|
reverseLang?: string
|
|
style: React.CSSProperties
|
|
}
|
|
|
|
export function GlossTip({ gloss, reverse, reverseLang, style }: Props) {
|
|
return (
|
|
<div
|
|
className="petal-gloss-tip pointer-events-none absolute z-20 px-2.5 py-1.5 text-sm"
|
|
role="tooltip"
|
|
style={{
|
|
maxWidth: 280,
|
|
background: 'var(--color-plum)',
|
|
color: 'var(--color-surface)',
|
|
borderRadius: 'var(--radius-input)',
|
|
boxShadow: 'var(--shadow-soft)',
|
|
lineHeight: 1.35,
|
|
fontFamily: "'Nunito','PingFang SC','Microsoft YaHei','Noto Sans CJK SC',sans-serif",
|
|
...style,
|
|
}}
|
|
>
|
|
{gloss}
|
|
{reverse && (
|
|
<span className="mt-0.5 block" style={{ opacity: 0.72, fontSize: '0.85em' }}>
|
|
{reverseLang ? `${reverseLang}: ` : ''}
|
|
{reverse}
|
|
</span>
|
|
)}
|
|
</div>
|
|
)
|
|
}
|