Files
zulip/help/configure-multi-language-search.md
Lauryn Menard dedea23745 help-docs: Move help center documentation to top level directory.
These files are not Jinja2 templates, so there's no reason that they needed
to be inside `templates/zerver`. Moving them to the top level reflects their
importance and also makes it feel nicer to work on editing the help center content, 
without it being unnecessary buried deep in the codebase.
2023-01-25 14:08:29 -08:00

21 lines
1006 B
Markdown

# Configure multi-language search
Zulip supports [full-text search](/help/search-for-messages), which can be
combined arbitrarily with Zulip's full suite of narrowing operators. By default,
Zulip search only supports English text, using [PostgreSQL's built-in full-text
search feature](https://www.postgresql.org/docs/current/textsearch.html), with a
custom set of English stop words to improve the quality of the search results.
Self-hosted Zulip organizations can instead set up an experimental
[PGroonga](https://pgroonga.github.io/) integration that provides full-text
search for all languages simultaneously, including Japanese and Chinese. See
[here](https://zulip.readthedocs.io/en/latest/subsystems/full-text-search.html#multi-language-full-text-search)
for setup instructions.
## Related articles
* [Configure organization language for automated messages and invitation emails][org-lang]
* [Searching for messages](/help/search-for-messages)
[org-lang]: /help/configure-organization-language