typesense / typesense/docusaurus-theme-search-typesense
i18n not working correctly
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 84
- Forks
- 24
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
Description
After installing docusaurus-theme-search-typesense 0.15.0-0 in docusaurus and setting i18n in docusaurus.config.js to "defaultLocale: 'zh-Hans', locales: ['zh-Hans ']" in docusaurus.config.js, the search box functions normally after publishing, but the search box UI still shows English.
If you add algolia node to the themeConfig (keep the typesense node), the search box UI can display the localized language normally, and the search is also using the typesense.
Expected Behavior
Following the locale configuration, the search box UI shows the corresponding language
For example, "Search docs" is displayed as "Search" in Chinese.
Actual Behavior
Metadata
Typesense Version:0.25.2
docusaurus-theme-search-typesense: 0.15.0-0
OS:Ubuntu 22
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the i18n settings in docusaurus.config.js and trace how the Typesense search theme receives the locale, comparing the behavior with the added Algolia configuration. Verify the search UI uses the configured Chinese locale with Typesense alone, while preserving search functionality after publishing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, localization, search
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100