#random

Escaping Encoding for Special Characters in Typesense

TLDR Nima asked about escaping encoding for special characters in Typesense. Kishore Nallan suggested checking raw response and mentioned that decoding might be needed before indexing.

3mo

Join the chat

Jun 13, 2023 (3 months ago)

Photo of md5-aaf4a8300f867ebf0c8d3e9f152943ee

Nima

05:55 AM

Hey guys
Is there a setting in Typesense where we can escape encoding for special characters.
Right now this is what we see:
Thank you

Image 1 for Hey guys<br>Is there a setting in Typesense where we can escape encoding for special characters.<br>Right now this is what we see:<br>Thank you

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

05:57 AM

Typesense does not apply any processing to the text during storage or during response. Can you please check the raw response returned from Typesense API?

Nima

06:12 AM

Is this way you mean?

Kishore Nallan

06:13 AM

Yes, as you can see, the document data already contains those encoded characters. Typesense just returns that content directly.

Nima

06:22 AM

So the problem is escaping it in the Jekyll nav.yaml file then?

Kishore Nallan

06:26 AM

Yes, so the HTML entities have to be decoded before being indexed. Let me also find out if there's a way to do this automatically within the docsearch scraper.

Nima

06:59 AM

It’s strange but the ampersand is rendered correctly

Kishore Nallan

10:30 AM

I will get back to you on this issue as well.

Nima

10:31 AM

thank you; I posted also to community just in case

Typesense

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

Indexed 2764 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

Handling Special Characters in Search Queries

Sidharth asks how to handle special characters in search queries. Kishore Nallan suggests using `symbols_to_index` configuration and provides an example to help.

4mo

Issue with Typesense Search and Special Characters

gab faced an issue with Typesense when searching with special characters. Jason and Kishore Nallan provided support and identified the issue as a bug. The problem was resolved after upgrading to `0.25.0.rc44`.

2mo

Special Character Impact on Indexing and Querying

Sergio suspects a special character may be affecting Typesense indexing and querying. Kishore Nallan requests a code snippet and advises creating an issue on GitHub.

7mo

Comma Escape Issue in Typesense with Instant Search Adapter

Stefan reports issues with comma escaping in Typesense instant search adapter. Kishore Nallan confirms the known issue with no available resolution yet.

29mo

Query on Typesense Indexing Special Characters

JinW inquired about Typesense indexing .(period) and synonyms stripping out the period, Jason clarified that from version 0.22, Typesense can index special characters and suggested using 0.22.0.rcs39.

22mo