# Why do non ASCII characters cause problems in elastic search?
**URL:** https://discuss.elastic.co/t/why-do-non-ascii-characters-cause-problems-in-elastic-search/291617
**Category:** Elasticsearch
**Created:** [December 13, 2021, 9:56am UTC](https://discuss.elastic.co/t/why-do-non-ascii-characters-cause-problems-in-elastic-search/291617 "2021-12-13T09:56:52Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Pineirin](https://discuss.elastic.co/u/Pineirin)
#### Post date: [December 13, 2021, 9:56am UTC](https://discuss.elastic.co/t/why-do-non-ascii-characters-cause-problems-in-elastic-search/291617/1 "2021-12-13T09:56:52Z")
Greetings.
I have found a problem in the search bar of my application (that uses Elasticsearch for the search bar).
If I do a fuzzy search of a text (in this case the title of a book) that is quite long (more than 96 characters) and that uses non ASCII characters (for example in my case, ®). I get the following error:
too\_complex\_to\_determinize\_exception: Determinizing automaton with 11390 states and 22957 transitions would result in more than 10000 states.
I've tried to find answer in google and in the documentation, but either there aren't or I'm not a good researcher, regardless. I would be grateful if I get an explanation into why this is happening.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [January 10, 2022, 9:57am UTC](https://discuss.elastic.co/t/why-do-non-ascii-characters-cause-problems-in-elastic-search/291617/2 "2022-01-10T09:57:49Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.