User Story
- As a reader in French, Arabic, or Japanese
- I want Dive to search and answer in my language
- So that the results are usable
Where in the flow: Language selection on the search screen; language drives which content is searched and which copy is shown.
Acceptance criteria
- The language in effect for Dive is the language the reader has selected for search, with no separate Dive-only language switch.
[] Changing language while the sheet is open cancels the in-flight request and re-queries in the new language.
TS: The current design means the user must dismiss the semantic search results sheet before they can switch languages.
- Arabic renders right-to-left throughout onboarding, the entry point, the explainer modal, the sheet, the passage cards — including the multi-level trail and its separators — the attribution row, and both feedback surfaces.
- Japanese passages, trails, and headings wrap and truncate following Japanese line-break rules rather than breaking on spaces.
- French diacritics and Arabic shaping are preserved through highlighting and truncation.
- Language is recorded on every logged event in the funnel.
Notes and open questions
[] The three-level trail ("Cat | Senses | Vision") gets long. Confirm how it truncates in Japanese and how the order and separators reverse in Arabic.
TS: Per our latest sync, we will only show a two-level trail (Article title and whatever section article is in, returned from the semantic search API.)
- Onboarding needs a localised worked example per language — see US-2.
Out of scope
Cross-language search (querying in one language and getting passages from another).
Design
N/A