# Content encoding issues

**URL:** https://discuss.elastic.co/t/content-encoding-issues/4854
**Category:** Elasticsearch
**Created:** [July 14, 2011, 3:21am UTC](https://discuss.elastic.co/t/content-encoding-issues/4854 "2011-07-14T03:21:46Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![jp\_lorandi](https://avatars.discourse-cdn.com/v4/letter/j/e480ec/32.png) [@jp\_lorandi](https://discuss.elastic.co/u/jp_lorandi)
#### Post date: [July 14, 2011, 3:21am UTC](https://discuss.elastic.co/t/content-encoding-issues/4854/1 "2011-07-14T03:21:46Z")

</div>

I'm currently attempting to index documents encoded with UTF-8 and I'm getting strange garbage out of \_source when retrieving data. Has anybody had the same problem? Which encoding does ES use out of the box?

TIA,JP

---

<div class="post-metadata">

### Author: ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)
#### Post date: [July 14, 2011, 3:22am UTC](https://discuss.elastic.co/t/content-encoding-issues/4854/2 "2011-07-14T03:22:47Z")

</div>

UTF8.

On Thursday, July 14, 2011 at 6:21 AM, [jp.lorandi@cfyar.com](mailto:jp.lorandi@cfyar.com) wrote:

> I'm currently attempting to index documents encoded with UTF-8 and I'm getting strange garbage out of \_source when retrieving data. Has anybody had the same problem? Which encoding does ES use out of the box?
> 
> TIA,  
> JP

---

<div class="post-metadata">

### Author: ![ppearcy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ppearcy/32/980_2.png) [@ppearcy](https://discuss.elastic.co/u/ppearcy)
#### Post date: [July 14, 2011, 3:48am UTC](https://discuss.elastic.co/t/content-encoding-issues/4854/3 "2011-07-14T03:48:38Z")

</div>

I can vouch that the encoding support is solid. Store English, various  
European, Chinese, Japanse in UTF8 with no problem. Most likely it is  
getting kludged client side. Do you see encoding issues when you  
execute from the browser with a JSON plugin?

On Jul 13, 9:22 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote:

> UTF8.
> 
> On Thursday, July 14, 2011 at 6:21 AM, [jp.lora...@cfyar.com](mailto:jp.lora...@cfyar.com) wrote:
> 
> > I'm currently attempting to index documents encoded with UTF-8 and I'm getting strange garbage out of \_source when retrieving data. Has anybody had the same problem? Which encoding does ES use out of the box?
> 
> > TIA,  
> > JP

---

<div class="post-metadata">

### Author: ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)
#### Post date: [July 14, 2011, 4:35am UTC](https://discuss.elastic.co/t/content-encoding-issues/4854/4 "2011-07-14T04:35:33Z")

</div>

No need to vouch :), can you provide a recreation?

On Thursday, July 14, 2011 at 6:48 AM, Paul wrote:

> I can vouch that the encoding support is solid. Store English, various  
> European, Chinese, Japanse in UTF8 with no problem. Most likely it is  
> getting kludged client side. Do you see encoding issues when you  
> execute from the browser with a JSON plugin?
> 
> On Jul 13, 9:22 pm, Shay Banon \<[shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) ([http://elasticsearch.com](http://elasticsearch.com))\> wrote:
> 
> > UTF8.
> > 
> > On Thursday, July 14, 2011 at 6:21 AM, [jp.lora...@cfyar.com](mailto:jp.lora...@cfyar.com) ([http://cfyar.com](http://cfyar.com)) wrote:
> > 
> > > I'm currently attempting to index documents encoded with UTF-8 and I'm getting strange garbage out of \_source when retrieving data. Has anybody had the same problem? Which encoding does ES use out of the box?
> > 
> > > TIA,  
> > > JP

---

<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: [July 6, 2017, 4:00am UTC](https://discuss.elastic.co/t/content-encoding-issues/4854/5 "2017-07-06T04:00:42Z")

</div>


