Re: Testing
By: Accession to deon on Thu Sep 10 2026 09:33 pm
Howdy,
Ah, ok. I only mentioned it because it looked like your automated reply removed the colon, or something. Either way, it wasn't the same as it was in his header.
Yes, so the display of the kludges in the test message response, is a "key"/"value" display, where the key is the kludge and the value is the kludges value.
The delimiter is the space, because the kludge inludes the colon, eg: MSGID:, TID:, PID:. When there is no space, clrghouz will fall back to delimit on the colon, hence why it was rendered as "AREA FSX_NET", because it was packed as AREA:FSX_NET, not AREA: FSXNET (with a space).
(AREA tags are not a \x01 kludge, so normally it is not included in the output, but in that packet it was included a second time as a kludge.)
Interesting though, the source message had two area tags:
Maybe that's why?
Yup, the first AREA tag was taken as the message area, the second was just kept verbatim (and parsed for the test output).
...ëîåï
--- SBBSecho 3.37-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)