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.
1
Jun 13, 2023 (6 months ago)
Nima
05:55 AMIs there a setting in Typesense where we can escape encoding for special characters.
Right now this is what we see:
Thank you
Kishore Nallan
05:57 AMNima
06:12 AM
Kishore Nallan
06:13 AMNima
06:22 AMKishore Nallan
06:26 AMNima
06:59 AMKishore Nallan
10:30 AMNima
10:31 AM1
Typesense
Indexed 3015 threads (79% resolved)
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.
Handling Special Characters in Typesense Queries
Jack had an issue with Typesense returning all results when querying with special characters. Jason indicated that Typesense removes special characters, suggesting a modification in the `symbols_to_index` setting. Jack found a solution by implementing a client-side filter for special characters only queries.
Debugging & Encoding Issue with Typesense and PHP
Digamber had an issue displaying "R&B" after adding as a facet. Kishore Nallan suggested the PHP client might be encoding the value. After some discussion, Digamber concluded that WordPress was the cause, encoding categories into HTML entities.
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`.
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.