Tatu Saloranta comments

Results 3337 comments of


                                            Tatu Saloranta

Can't tell non-blocking parser what charset to use for decoding input

Yes, you can not define other encodings so it only works for UTF-8 and 7-bit ASCII (since that is a subset). This is a fundamental limitation and it is unlikely...

Can't tell non-blocking parser what charset to use for decoding input

Right. Vast majority of JSON really should be UTF-8, especially considering that only officially standard legal charsets are UTF-8, UTF-16 and UTF-32 (as per original JSON specification). But there are...

`UTF8JsonGenerator` writes supplementary characters as a surrogate pair -- should use 4-byte encoding

Yes. Unfortunately this is how JSON specification mandates escaping of these characters: "To escape a code point that is not in the Basic Multilingual Plane, the character is represented as...

`UTF8JsonGenerator` writes supplementary characters as a surrogate pair -- should use 4-byte encoding

Hmmh. Ok, fair enough. I am not a fan of using somewhat broken escaping anyway... So it does seem like output could be changed. But just in case some code...

`UTF8JsonGenerator` writes supplementary characters as a surrogate pair -- should use 4-byte encoding

Quick note: hoping to fix this before 2.7.0-rc1 goes out, which is to happen soon (ideally within a week or so but we'll see).

`UTF8JsonGenerator` writes supplementary characters as a surrogate pair -- should use 4-byte encoding

Ok. Turns out that the fix is not quite as easy as I had hoped. I forgot that the thing that makes this complex is the requirement to have access...

`UTF8JsonGenerator` writes supplementary characters as a surrogate pair -- should use 4-byte encoding

Sort of related, #307.

`UTF8JsonGenerator` writes supplementary characters as a surrogate pair -- should use 4-byte encoding

@fiserro I haven't had time to work on this and have nothing planned.

`UTF8JsonGenerator` writes supplementary characters as a surrogate pair -- should use 4-byte encoding

@rkinabhi It is something that would be nice to resolve but I am not actively working on it at this point (I try to add `active` label on things I...

Add `JsonReadFeature.ALLOW_JDK_WHITESPACE` (or equivalent)

These characters are not considered whitespace according to JSON specification, which is why they are not ignored by default. But if these are in widespread usage (character code is white...