Subj : Re: More Questions
To   : TRACKER1
From : the doctor
Date : Wed Apr 06 2022 14:59:00

>--- TRACKER1 wrote ---
> On 2/24/22 08:44, the doctor wrote:
> I can't speak for how Synchronet is handling this...
> 
> I have been looking into this as well, planning on cataloging the 
> information into a couple services as well.  My plan was to look for 
> "json-begin" and "json-end" in the message and plucking what's in 
> between.
> 
> Per the JSON spec, it *should* be UTF8 encoded, and any white-space 
> characters outside quoted strings should be ignored.  Since you can 
> escape any character outside the 7-bit ASCII range (as well as quotes) 
> per JS encoding (\x## \u#### \###), I suggest doing so for any 
> interchange messages that include higher characters (and control chars), 
> and (re)encoding any non-utf8 character sets to their Unicode 
> corresponding values.
> 
> As to message bodies, I think that terminal based message conventions is 
> the combination of CRLF (\r\n), since \r will move the cursor to the 
> beginning of the line and \n will move the cursor down one line. (IIRC)
> 
> That's just my own opinionated take on this one, and what I've been 
> doing so far.

Thanks for the information.  I will trying doing what you suggest for
unicode characters.  I've more or less got it working now, it was really
a problem caused by the more dusty bits of code (that i wrote like 15 or
more years ago) and me not remember what I did or why. (:


---
"No matter where you go, there you are..."


---
* TARDIS BBS - Home of QUARKware * telnet bbs.cortex-media.info
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.