skills/ca-property-tax-appeal/references/multilingual-support.md

# Multilingual support

Use these rules before the preparation screen and throughout the case.

## Language setup

If the user's message clearly establishes a preferred language, continue in that language. Show one unobtrusive status line:

> Language: Español — you can change this at any time.

Translate the status line into the selected language. Do not ask the user to confirm an obvious language choice.

If the language is unclear, mixed in a way that prevents a confident choice, or the user requests options, ask only:

```text
Choose your language / 请选择语言 / Elija su idioma / Chọn ngôn ngữ:

1. English
2. 简体中文
3. 繁體中文
4. Español
5. Tiếng Việt
6. 한국어
7. Tagalog / Filipino
8. Bilingual / 双语 — English plus another language
9. Another language — type its name
```

After selection, show the normal preparation screen. Do not ask for the property address in the language-selection reply.

## Language continuity

- Use the selected language for explanations, questions, progress labels, summaries, and preparation lists.
- Accept `change language`, `换语言`, `cambiar idioma`, or the equivalent at any time.
- On a language change, confirm the new language in one short line and resume the same stage. Preserve all collected facts, documents, source links, deadlines, and warnings.
- Never infer language from a person's name, ethnicity, address, or property location.
- When the user mixes languages intentionally, keep their established preference or ask one short clarification only when comprehension would change the answer.

## Bilingual mode

When the user requests bilingual mode, ask which second language they want if it is not already clear. Use the user's language first, followed by concise English. Avoid duplicating long evidence tables; translate headings and explanations while keeping shared numbers, addresses, and source links once.

## Official terms and records

- Preserve exact English names for agencies, forms, portals, statutory labels, and official form fields. Add a plain-language translation in parentheses on first use.
- Do not translate property addresses, parcel/APN values, case numbers, dollar amounts, percentages, or URLs.
- Show critical dates with an unambiguous English or translated month name plus ISO format when helpful, for example `August 31, 2026 (2026-08-31)`.
- Explain an English notice or form in the selected language, but quote the exact English field label the user must locate.
- Keep direct-source citations attached to the translated claim.

## Submission-language safety

- Do not assume a county accepts an appeal application, supporting statement, testimony, or evidence index in the user's preferred language.
- Verify current official language-access and filing rules before stating that non-English submission text is accepted.
- Prepare the filing version in an officially accepted language. When acceptance cannot be verified, default the filing-ready draft to English and provide the selected-language explanation separately.
- Label any non-official rendering `Unofficial translation for understanding` in the selected language.
- Never claim interpreter availability, translation accuracy certification, or accommodation rights without a current official source.

## Translation quality

- Prefer short, familiar words over literal legal translation.
- Preserve meaning, values, dates, evidence strength, deadlines, risks, and uncertainty exactly.
- Do not soften warnings or strengthen conclusions during translation.
- If a specialized term is uncertain, keep the English term and explain it plainly instead of inventing a translated legal term.
- Ask the user to correct a misunderstood dialect, script, or term without restarting the case.