Feature Request: Add Korean Tokenization Support to Built-in Search #3951
KahyeonYu
started this conversation in
Feature Requests
Replies: 1 comment
-
|
Plus one for this. If we are providing multiple translations on our docs site then multi-lingual search should work as well. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
We would like to request native Korean tokenization support in Mintlify’s built-in search.
After contacting the Mintlify team, we were informed that the current search implementation does not provide Korean-specific tokenization or language-specific search configuration options. As a result, Korean search queries fail to return accurate and relevant results.
Current Limitation
According to the response from the Mintlify team:
The built-in search does not support Korean tokenization.
There are no language-specific search configuration options.
Improving search by manually adding more keywords in content is currently the only suggested workaround. (but this won't fully address Korean tokenization needs)
In practice, this leads to:
Inconsistent search results depending on spacing or wording variations.
Difficulty discovering relevant documentation even when content clearly contains the intended concept & keywords
Because Korean queries are not properly tokenized, search accuracy is significantly lower compared to English queries.
Requested Improvements
We would like Mintlify to provide one or more of the following:
Native Korean tokenization support in the built-in search index.
Why This Matters
Search is a core navigation mechanism in documentation.
Without accurate Korean search support, the overall user experience for Korean-speaking users is significantly impacted.
Beta Was this translation helpful? Give feedback.
All reactions