Yes, that does look like plain ASCII* (please use <code> tags next time, and consider registering an account so you can edit posts).
So the problem is less likely to be on the input end, but you also haven't shown us any code. I think we need to take a step back here - please see Short, Self-Contained, Correct Example and post the shortest piece of code possible that still reproduces the issue, some short sample input data, the output data corresponding to that input which shows the problem (a hex dump might be best to see the null bytes, or at least the output of Data::Dump), and the output that you actually want to get for that input. More advice in How do I post a question effectively? and I know what I mean. Why don't you?
* Update: I missed it earlier, but the AM post is correct that if you have bytes above 0x7f, then it's not plain ASCII. If Encode::Guess is guessing ASCII, and you used my example code, then probably the buffer size was not big enough. When I said "Can you show us?", I actually meant that part of the file which contains bytes above 0x7f.
In reply to Re^4: Parsing issue (updated)
by haukex
in thread Parsing issue (null bytes?)
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |