# BytesToString corrupting  EDI Data

**URL:** <https://techcommunity.softwareag.com/t/bytestostring-corrupting-edi-data/107907>\
**Category:** Forum\
**Tags:** EDI\
**Created:** [March 13, 2003, 12:29am UTC](https://techcommunity.softwareag.com/t/bytestostring-corrupting-edi-data/107907 "2003-03-13T00:29:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![chris18](https://avatars.discourse-cdn.com/v4/letter/c/e8c25b/32.png) [@chris18](https://techcommunity.softwareag.com/u/chris18)\
**Post date:** [March 13, 2003, 12:29am UTC](https://techcommunity.softwareag.com/t/bytestostring-corrupting-edi-data/107907/1 "2003-03-13T00:29:28Z")

</div>

I’m experiencing a problem where bytesToString is  
corrupting my segment terminators on inbound EDI data.  
Has anyone experience this? Is there some encoding that I  
have to specify and if so what?

Thanks.

---

<div class="post-metadata">

**Author:** ![reamon](https://avatars.discourse-cdn.com/v4/letter/r/b77776/32.png) [@reamon](https://techcommunity.softwareag.com/u/reamon)\
**Post date:** [March 13, 2003, 12:30am UTC](https://techcommunity.softwareag.com/t/bytestostring-corrupting-edi-data/107907/2 "2003-03-13T00:30:05Z")

</div>

Try ISO-8859-1 as the encoding.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 2, 2021, 3:04pm UTC](https://techcommunity.softwareag.com/t/bytestostring-corrupting-edi-data/107907/3 "2021-04-02T15:04:58Z")

</div>