Github user HyukjinKwon commented on the issue:
    Wait .. do we formally support UTF-16 encoded files in line by line parsing 
via JSON? I think this accidentally works because the newline character in 
UTF-8 is the part of UTF-16.
    I think I am fine to revert it but how about we avoid adding a test?


To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to