Max

In case it's useful, @pmichalek's image can be made readable by copying all black pixels 1 px to the right and then again copying all black pixels 1 px down:...

Also forgot to mention, I think I've made all the necessary updates to the basic string manipulation operations such as searching, concatenating, splitting, indexing. I've also updated `@base64` and `fromjson`...

For the record, the CI failures above are environmental. 3 of the 6 Travis CI builds passed. The other 3 Travis CI builds and the 2 AppVeyor builds failed for...

Force pushed because I forgot to include replacement character emissions in `@base64` and `utf8bytelength`. Also removed an unnecessary static function in `jv_parse.c`.

I've gone ahead and added another commit to do the aforementioned normalisation of UTF-8/UTF-16 errors into well-formed UTF-8 during string concatenation. Also took the opportunity to optimise part of the...

Should also point out that my last commit pretty much makes the `jvp_utf8_backtrack` mechanism obsolete, since the invalid bytes are stored and corrected on concatenation. This means that #2259 is...

> A conformant process must not interpret illegal or ill-formed byte sequences as characters My implementation does not interpret illegal or ill-formed byte sequences as characters. It interprets both as...

> `jq` should not behave differently based on the encoding of the input. I'm not sure I understand your issue here. Where do you think it behaves differently based on...

> I did not look at the code. Your the one who said it behaved differently in the passage I quoted ("UTF-8 errors are maintained and UTF-16 errors are converted...

> Yes it does cause this to happen. It could be a string with an invalid byte, which you end up passing to match, for example. `match` doesn't currently see...