Every `中文 · English` string moves out of ~29 components into web/src/i18n: one Pack type, a verbatim zh pack, and two ways to read it — usePack() for components, pack() for the modules that build a line when something happens rather than when something renders. Anything with a value in it is a function on the pack rather than a template at the call site, English pluralisation included: word order isn't universal, and a pack author has to be able to move the number. The roster constants (tones, rewrite styles, export formats, companions) keep only value + emoji, so a label can't drift from its key. On the server, internal/llm/lang.go replaces "Simplified Chinese" in the three prompts that actually name her language. pt-PT is spelled "European Portuguese (pt-PT, never Brazilian Portuguese)" in the prompt itself, and each Lang carries her word for "why" so the tutor prompt still recognises the question when she asks it her way. pair_lang reaches the model through the row-scoped query each handler already ran — the one that proves she owns the document — rather than a second lookup that could disagree with it. Also records Phase 18's deploy: migration 0011 rehearsed against a copy of the live VPS database, then applied for real.
24 lines
726 B
Go
24 lines
726 B
Go
package llm
|
|
|
|
import (
|
|
"context"
|
|
)
|
|
|
|
// RunTranslate renders a short English explanation into the writer's own
|
|
// language. It is a one-shot Complete (the result seeds the Ask Petal bubble),
|
|
// kept at a low temperature so the translation is faithful rather than creative. Output is
|
|
// trimmed of any stray surrounding quotes the model may add.
|
|
func RunTranslate(ctx context.Context, client LLMClient, text string, lang Lang) (string, error) {
|
|
out, err := client.Complete(ctx, CompletionRequest{
|
|
Messages: TranslateMessages(text, lang),
|
|
MaxTokens: 512,
|
|
Temperature: 0.2,
|
|
TopP: 0.9,
|
|
RepetitionPenalty: 1.1,
|
|
})
|
|
if err != nil {
|
|
return "", err
|
|
}
|
|
return cleanRewrite(out), nil
|
|
}
|