added new utf8 test cases that simulate 1-4 byte utf8 characters being chunked before their boundaries are reached, which leads the subsequent call to buffer.toString() to display two-four replacement characters: �� instead of the proper representation of the multi-byte characters that were actually passed to the parser
added detection & correction of multi-byte utf8 characters that are split up (when chunked in stream buffers) before the character boundary is met, this commit passes existing tests and new tests written for this use case
Merge pull request #14 from jlank/utf-boundary

utf8 boundary patch