0.13.22 — results in the page's language

Semantic vectors can be shared by all language versions of an instance. That is a deliberate choice: the model is multilingual and the entry key is the identity of the material above language, so a question in English hits the same entry as a question in Polish. A separate index per language would be the same content computed twice — and it would weigh twice in the bundle.

The catch is that a vector chunk carries the text it was computed from, and the result showed exactly that text. In a version without its own vectors, a reader asked in English and got a snippet in Polish.

Since 0.13.22 the title, address and snippet always come from the entry in the page's language. The matched paragraph is carried over by position: the chunk is literally a paragraph of the source entry, and the translation keeps the paragraph layout, so it is enough to find its place and take the paragraph with the same number. When the layouts do not match, the entry's excerpt is shown instead of text in another language. An entry that does not exist in the given language does not make it into the results — the next one takes its place.

The snippet trimming from 0.13.18 now works on text in the page's language, so the window lands on the sentence that shares a word stem with a question asked in the same language.