Timeline for How to process JSON with strings containing invalid UTF-8
Current License: CC BY-SA 4.0
19 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 18, 2023 at 11:39 | history | edited | Stéphane Chazelas | CC BY-SA 4.0 | added 1392 characters in body |
| Nov 17, 2023 at 12:37 | history | edited | Stéphane Chazelas | CC BY-SA 4.0 | added 2 characters in body |
| Nov 17, 2023 at 9:32 | history | edited | Stéphane Chazelas | CC BY-SA 4.0 | added 263 characters in body |
| Oct 11, 2023 at 13:34 | history | edited | Stéphane Chazelas | CC BY-SA 4.0 | added 1 character in body |
| Oct 3, 2023 at 11:24 | answer | added | Philip Couling | timeline score: 2 | |
| Oct 3, 2023 at 5:58 | answer | added | Stéphane Chazelas | timeline score: 2 | |
| Oct 1, 2023 at 12:40 | history | edited | Stéphane Chazelas | CC BY-SA 4.0 | added 419 characters in body |
| Oct 1, 2023 at 7:56 | history | edited | Stéphane Chazelas | CC BY-SA 4.0 | added 8 characters in body |
| Oct 1, 2023 at 7:38 | history | edited | Stéphane Chazelas | CC BY-SA 4.0 | added 9 characters in body |
| Oct 1, 2023 at 7:32 | history | edited | Stéphane Chazelas | CC BY-SA 4.0 | added 87 characters in body |
| Oct 1, 2023 at 7:16 | history | edited | Stéphane Chazelas | CC BY-SA 4.0 | added 9 characters in body |
| Oct 1, 2023 at 6:58 | history | edited | Stéphane Chazelas | CC BY-SA 4.0 | added 672 characters in body |
| Sep 30, 2023 at 16:25 | history | edited | Stéphane Chazelas | CC BY-SA 4.0 | added 184 characters in body |
| Sep 30, 2023 at 15:22 | history | edited | Stéphane Chazelas | CC BY-SA 4.0 | added 392 characters in body |
| Sep 30, 2023 at 15:17 | comment | added | Stéphane Chazelas | @StephenHarris changing the locale is a good point though that I've not much tested. For instance, with column, switching to a locale using latin1 as charset is a way to get the same raw (and invalid as JSON) format as with util-linux utilities instead of the one with ambiguous non-reversible escaping one you get in UTF-8 locales. | |
| Sep 30, 2023 at 14:59 | comment | added | Stéphane Chazelas | @StephenHarris, JSON is meant to be in UTF-8 regardless of the locale. There are probably tools that take into account the locale when decoding strings before producing the JSON, but using the C locale, is more likely to harm than help as C locales usually don't specify characters other than the ASCII ones. | |
| Sep 30, 2023 at 14:57 | answer | added | Stéphane Chazelas | timeline score: 2 | |
| Sep 30, 2023 at 14:56 | comment | added | Stephen Harris | Does this behaviour change if you set LANG=C or to another locale? I've found many tools work "better" in C/POSIX locale. | |
| Sep 30, 2023 at 13:40 | history | asked | Stéphane Chazelas | CC BY-SA 4.0 |