Rob Hulswit

With the current commits, the following test will fail: ```js let i = 0; const testStr = "\xc2\x80"; // when stored in 1-byte chars, this is a valid UTF-8 encoding...

The problem is the latin1 decoder is used for the Windows-1252 codepage. Those encodings are not equivalent, especially for characters 0x80-0x9F. These are not in use for latin1 / ISO...

Using the `{ stream: true }` option in `decode()` permanently disables the latin1 fast path for a TextDecoder, so the following workaround is possible: ``` const decoder = new TextDecodere(encoding);...

@KunalKumar-1 that's right, I hadn't read the standard yet when I wrote that comment. To adhere to the standard, a correct Windows-1252 decoder should be used in all those cases....