Problems getting Chinese search to work without warnings

[RonaldLN]

The following is the information displayed in the terminal

$ mkdocs gh-deploy --force
INFO    -  Option search.lang 'zh' is not supported, falling back to 'en'
WARNING -  Language 'zh' is not supported by lunr.js, not setting it in the 'plugins.search.lang' option
Building prefix dict from E:\Github\MyPamphlet\jieba_dict\dict.txt.big ...
DEBUG:jieba:Building prefix dict from E:\Github\MyPamphlet\jieba_dict\dict.txt.big ...

[squidfunk]

Not sure without knowing how you configured the project. Please create a minimal reproduction and attach it to this discussion.

[RonaldLN]

Is that it? I don't know if I made a mistake when creating a reproduction

9.3.1-search-cant-support-chinese.zip

[squidfunk]

Chinese search support is not implemented via Lunr.js but via a custom impementation that segments text during the build. Here's an explanation why this is not supported in Lunr.js. If you just remove the lang setting from the search plugin, Chinese search should work correctly, as the search plugin will use jieba automatically.

[RonaldLN]

Do you mean that I should be like this？
Change

- search:
      separator: '[\s\-,:!=\[\]()"/]+|(?!\b)(?=[A-Z][a-z])|\.(?!\d)|&[lg]t;'
      jieba_dict: jieba_dict/dict.txt.big
      jieba_dict_user: jieba_dict/user_dict.txt
      lang: 
        - zh
        - ja
        - en

to

- search:
      separator: '[\s\-,:!=\[\]()"/]+|(?!\b)(?=[A-Z][a-z])|\.(?!\d)|&[lg]t;'
      jieba_dict: jieba_dict/dict.txt.big
      jieba_dict_user: jieba_dict/user_dict.txt
      lang: 
        - ja
        - en

[RonaldLN]

Oh, I seem to understand. Should it be removing the entire lang setting?

[squidfunk]

Yes.

[RonaldLN]

I just discovered another issue. The site language selector I am using is based on the i18n plugin,
This is part of my configuration

plugins:
  - i18n:
      default_language: en
      material_alternate: true
      languages:
        zh:
          name: 简体中文
          build: true
        en:
          name: English labels (英文标签)
          build: false

Then it will cause similar errors as before

And when I remove this plugin, there won't be this error message.
I use this plugin instead of this
because it allows me to share the same version of .md files in both language modes, while setting up versions in both languages for some documents,
for example,

└─doc
    ├─index.md
    ├─index.zh.md
    ├─doc1.md
    └─doc2.md

Like this, the index page will have two language versions, while doc1 and doc2 share the same version in both languages.
So my question is, can functions like this be implemented without the i18n plugin, or can error messages be resolved with using the i18n plugin (thus enabling normal use of Chinese search support)