typesense

Even need to support more language (not only two) in same time,
I want to make a global service.

You can just leave the `locale` parameter in the field definition in the collection schema blank

Then Typesense will go off of unicode character matches. But not sure how well this works with Chinese since it uses non-space tokenization

But Chinese and English is most important to me. <@U01NZ4D0LDD>

Using two locales at the same time on a single field isn't supported. So what Jason was suggesting would be the best in-between solution for your specific use-case. Otherwise, breaking the field into two separate fields, one for english and another one for Chinese locales could be an option