# Example of a UTF8 text which does not generate tokens

**URL:** <https://discuss.elastic.co/t/example-of-a-utf8-text-which-does-not-generate-tokens/192965>\
**Category:** Elasticsearch\
**Created:** [July 30, 2019, 6:33pm UTC](https://discuss.elastic.co/t/example-of-a-utf8-text-which-does-not-generate-tokens/192965 "2019-07-30T18:33:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![germax](https://avatars.discourse-cdn.com/v4/letter/g/a4c791/32.png) [@germax](https://discuss.elastic.co/u/germax)\
**Post date:** [July 30, 2019, 6:33pm UTC](https://discuss.elastic.co/t/example-of-a-utf8-text-which-does-not-generate-tokens/192965/1 "2019-07-30T18:33:31Z")

</div>

I have a text ಪೋರ್ಟ್‌ಲ್ಯಾಂಡ್‌ which passes the utf-8 encoding checks and causes no issues when I use it inside javascript or print to the console. However, elasticsearch cannot build a token from it and throws no alerts or errors.  
When I try to paste it in Kibana UI console it highlights the problematic spot in this text string:  
 ![kibana%20screenshot](https://us1.discourse-cdn.com/elastic/original/3X/6/4/64172a7cfdb085a65928514d65656144aa27d013.png)  
Yet, no errors or warnings are fired, the search simply yields no matches.

Are there any special utf8 characters present in this string that have to be escaped? It does not seem to have usual suspects as . {} / \

I am most concerned that no warnings are given, caught this issue by a pure accident

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 27, 2019, 6:33pm UTC](https://discuss.elastic.co/t/example-of-a-utf8-text-which-does-not-generate-tokens/192965/2 "2019-08-27T18:33:31Z")

</div>

Closed on August 27, 2019, 6:33pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.