Sujet : Re: tdom encoding
De : rich (at) *nospam* example.invalid (Rich)
Groupes : comp.lang.tclDate : 17. Dec 2024, 05:59:22
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vjr0fa$1i1a9$3@dont-email.me>
References : 1 2 3
User-Agent : tin/2.6.1-20211226 ("Convalmore") (Linux/5.15.139 (x86_64))
saito <
saitology9@gmail.com> wrote:
On 12/16/2024 9:13 PM, greg wrote:
Hello,
The unknown character is 007 or BELL.
Probably not allowed as a char in string.
Instead: \u0007
Gregor
Thank you and Rich for the wonderful info and the code.
The json data is what I receive from an api. I first thought it had
to do with encoding issues. It happens frequently so I maybe I will
ask them to be more careful with their json data generation.
If you are getting it from an API then you've found a bug if the API
is /really/ sending raw control characters as part of a JSON string.
tdom encoding
Re: tdom encoding