Issue with Typesense, Facets, and Special Characters

TLDR Ailish is encountering an issue with Typesense handling of apostrophes versus single quotes. Jason clarified how Typesense handle special characters and requested further specifics from Ailish.

Powered by Struct AI
Apr 11, 2022 (21 months ago)
Photo of md5-7fcbf02da67845f42ef837fd8a989396
12:14 PM
Is this a InstantSearch issue? My facets show up separately when there is an apostrophe vs a single quotation mark in the field. The Typesense results do not recognise the difference when I select either or both of these facets, and always shows me the total sum of results (682). So I assume the data is normalised on the Typesense side. However, Algolia document that they also normalise the data, so is it some limitation of faceting? Has anyone experienced this before?
Photo of md5-8813087cccc512313602b6d9f9ece19f
05:22 PM
Ailish Typesense only normalizes accented chars into their non-accented versions... It does not do this with apostrophes vs quotes
05:24 PM
Could you look at the network tab in your browser's dev console, and share the exact query made to Typesense when you select both filters? And also the response from Typesense?