# How could winlogbeat 5.0 support chinese character?

**URL:** <https://discuss.elastic.co/t/how-could-winlogbeat-5-0-support-chinese-character/49524>\
**Category:** Beats\
**Tags:** winlogbeat\
**Created:** [May 9, 2016, 7:46am UTC](https://discuss.elastic.co/t/how-could-winlogbeat-5-0-support-chinese-character/49524 "2016-05-09T07:46:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![zhanght1](https://avatars.discourse-cdn.com/v4/letter/z/958977/32.png) [@zhanght1](https://discuss.elastic.co/u/zhanght1)\
**Post date:** [May 9, 2016, 7:46am UTC](https://discuss.elastic.co/t/how-could-winlogbeat-5-0-support-chinese-character/49524/1 "2016-05-09T07:46:25Z")

</div>

How could winlogbeat 5.0 support chinese character?  
BR

---

<div class="post-metadata">

**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\
**Post date:** [May 9, 2016, 1:20pm UTC](https://discuss.elastic.co/t/how-could-winlogbeat-5-0-support-chinese-character/49524/2 "2016-05-09T13:20:03Z")

</div>

It should work with characters. For example, here's a [blog post](http://dev.classmethod.jp/server-side/elasticsearch/winlogbeat-release/) showing 1.1.0 being used with Japanese characters.

Messages from Windows are UTF-16, those are converted to UTF-8, and then the whole event is encoded as JSON and sent to Elasticsearch.

---

<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 5, 2017, 9:52pm UTC](https://discuss.elastic.co/t/how-could-winlogbeat-5-0-support-chinese-character/49524/3 "2017-07-05T21:52:14Z")

</div>