# Character encoding TC - Node

**URL:** <https://discuss.elastic.co/t/character-encoding-tc-node/9200>\
**Category:** Elasticsearch\
**Created:** [October 1, 2012, 11:59am UTC](https://discuss.elastic.co/t/character-encoding-tc-node/9200 "2012-10-01T11:59:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lukas\_Vlcek1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukas_vlcek1/32/819_2.png) [@Lukas\_Vlcek1](https://discuss.elastic.co/u/Lukas_Vlcek1)\
**Post date:** [October 1, 2012, 11:59am UTC](https://discuss.elastic.co/t/character-encoding-tc-node/9200/1 "2012-10-01T11:59:52Z")

</div>

Hi,

should I bother with character encoding when Transport Client talks to  
Node(s)? Say that -Dfile.encoding is setup differently on machines that run  
TC and Node. Could this make any harm?

I tried to look at elasticsearch starting scripts and did not find any JVM  
startup parameter relevant to encoding, thus the default system encoding is  
probably used by the JVM. So I assume that ES handles this internally at  
the communication binary protocol level. But I would like to double-check.

Regards,  
Lukas

--

---

<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, 3:10am UTC](https://discuss.elastic.co/t/character-encoding-tc-node/9200/2 "2017-07-06T03:10:38Z")

</div>

Closed on July 6, 2017, 3:10am UTC