Fill the 463 empty strings in the ar and ar-BH locales.
Placeholders and Arabic plural forms follow the existing file conventions;
technical parameter names (top_k, max_tokens, ...) are kept as-is.
Co-authored-by: Omar Albarghouthi <ThisisOmar-here@users.noreply.github.com>
A tool picked from the Integrations menu before the first message of a new chat stayed on only until the user left that chat. Coming back, the chat fell back to the model's default tools, so the tool was no longer offered to the model and the changed tool list broke prompt caching. The Web Search toggle was dropped the same way, and a picked skill was lost on reload. The picks are now kept for the chat from its first message on, like picks made later in the chat.
Citations from external knowledge bases (Qdrant, Milvus, pgvector) whose source is a web address showed that full address in the source list below the answer, while the numbered citation markers in the answer text already showed the page title. The source list now shows the same title. Because of that, these citations no longer add a site icon to the sources button, which matches regular knowledge bases. Web search results keep showing their address.
Fixes https://github.com/open-webui/open-webui/issues/32231
New **pt-BR** translations for items introduced in the latest releases, plus a consistency/quality pass across existing strings (grammar, tone, capitalization, pluralization). Placeholders and hotkeys preserved. No logic changes.
Rich UI tool embeds always tried to pass the arguments the model called the tool with into the embedded page, even when the browser does not allow it: with "iframe Sandbox Allow Same Origin" off (the default), or when an external tool embeds a page from another site. Each load then logged an uncaught SecurityError in the console. The arguments are now passed only where the browser allows it and skipped otherwise. The embed itself renders and behaves the same as before.
Fixes#32222
The Top K Reranker description under Admin Panel > Settings > Documents said it is the number of hybrid results sent to the reranker, but it is the number of chunks the reranker keeps per query and passes to the model. The Top K description did not say that with hybrid search it is also the number of candidates retrieved for the reranker. Admins following the old text set something like 15 / 3 and gave the model only 3 chunks per query. Both descriptions now say what the settings do, in English and German.
Fixes#32221
