#community-help

Understanding Locales Supported by Typesense

TLDR Carl-Gerhard asked about locales supported by Typesense. Kishore Nallan confirmed support for some locales and clarified they don't handle singular/plural differences.

13mo

Join the chat

Nov 11, 2022 (13 months ago)

Photo of md5-4000d03c20271e9897f2283858cf9d82

Carl-Gerhard

11:14 AM

Hey,

I have been trying to figure out what locales Typesense support. Can’t find anything documented about different locales.

Only thing I can find is when creating a new collection each field have a "locale": "" . Tried using this with the JS client but getting typescript error that locale does not exist on CollectionFieldSchema .

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

11:15 AM

👋 We have been working with users of specific locales to add support for some of them.

There's decent support for Korean, Thai and Cyrillic. What locale are you looking for?

11:16

Kishore Nallan

11:16 AM

Support for Mandarin and Japanese also exist but we have not had as much feedback for those yet.

Carl-Gerhard

11:19 AM

Swedish

Kishore Nallan

11:20 AM

For European languages we do basic normalization (e.g. handling accented characters etc.) -- do you face any specific issues when you index and search on Swedish without specifying any field locale?

Carl-Gerhard

11:26 AM

I tried the typo feature and feels like it does not give me great results back.

And search for a pluralized word when it’s indexed as singular

11:26

Carl-Gerhard

11:26 AM

But basic searches works fine

Kishore Nallan

11:27 AM

We don't explicitly handle singular/plural for any locale. Unless the singular/plural falls into the ambit of typo correction, like often in English (e.g. trailing "s")

Carl-Gerhard

11:34 AM

Okej, well thanks for the quick replies! Will play around with it

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 3015 threads (79% resolved)

Join Our Community

Similar Threads

Understanding Typesense Language Search and Locale

Juri inquired about language search in Typesense, and Kishore Nallan clarified it requires a locale to index certain languages. Discussion also included how to specify these locales and that multiple languages can be searched without decreasing performance.

22mo

Typesense Support for Non-English Languages

omega enquired about Typesense's support for non-English languages. Kishore Nallan suggested using separate fields for different languages.

15mo

Typesense Support for Japanese and Chinese Languages

Juri inquires about the potential of Typesense not supporting Japanese and Chinese-only applications. Kishore Nallan assures that support for CJK languages is under alpha testing, and already has some available use though not publicly documented yet.

33mo

Implementing Multilingual Texts in Typesense

Juri wants to implement bilingual text for a blog platform in Typesense. Kishore Nallan suggests creating different fields for each language. After some discussion, it is agreed to use different fields for complex languages requiring tokenization, while combining other languages. They have also discussed possibly disabling typo tolerance for some languages.

20mo

Typesense Support for Chinese, Japanese, and Korean Languages

Pete inquired about logographic support in typesense. Jason advised that the support is evolving based on feedback and suggested indexing data for testing and providing feedback.

15mo