Andrew Hodgkinson

> I don't know the original motivation, but keep in mind if reading an exact number of bytes from multi-byte encodings, you may wind up with invalid data in your...

A very good question and after a few hours I finally figured it out. ## The TL;DR (ish) CSV uses `IO#gets`. It appears that this _does_ obey encoding with files...

As far as the error in Ruby documentation goes: https://bugs.ruby-lang.org/issues/18833

@jrochkind: > it would return `length` codepoints, not length bytes. Exactly right. The `IO#gets` core library documentation on the `limit`  parameter has _only one word_ which is incorrect - it...

The Ruby issue got rejected because they say that `gets` etc. _do_ read in bytes, but _do not_ split across multibyte chunks and it seems that this will happily lead...

Found the issue & can create a PR with test cases, but there's a bit of discussion about how to handle it since we have two overlapping issues now. ##...

(Bump) Any interest in this? It's quite important to us (various encoding issues discovered down the chain - see referenced Down gem PR and subsequently linked issue https://github.com/janko/down/issues/73). Thanks!

It's been almost 3 years now. Someone even submitted a PR. What gives?!

We have a similar issue with v4.5.2 of the gem: ``` 852 | # SassC::SyntaxError: 853 | # Error: style declaration must contain a value 854 | # on line...

Since we've got to be streaming, then perhaps something as @felixbuenemann describes, with a `headers:` option; but perhaps it takes either strings in the Array, or Hashes which provide attributes...