Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Rich <rich@example.invalid>
Newsgroups: comp.lang.tcl
Subject: Re: tdom encoding
Date: Tue, 17 Dec 2024 04:59:22 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 20
Message-ID: <vjr0fa$1i1a9$3@dont-email.me>
References: <vjqf00$1c0s9$1@dont-email.me> <vjqmnq$1dblc$1@dont-email.me> <vjr001$1ibvi$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 17 Dec 2024 05:59:22 +0100 (CET)
Injection-Info: dont-email.me; posting-host="876264b18c00e4986a1fe1d9ed3feb32";
	logging-data="1639753"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+WS0KmLyKPSM+DKvhgXes1"
User-Agent: tin/2.6.1-20211226 ("Convalmore") (Linux/5.15.139 (x86_64))
Cancel-Lock: sha1:nrM9XJUpzcGKMZ9QVRJ4ORokQoE=
Bytes: 1617

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.