Subj : Hub Robot Report
To   : deon
From : Oli
Date : Sun Aug 29 2021 09:18:34

deon wrote (2021-08-29):

 d>    Re: Hub Robot Report
 d>    By: Oli to deon on Sat Aug 28 2021 03:52 pm

 Ol>> Your Hub Robot does not understand UTF-8
 Ol>>   ¿
 Ol>> ¿¿
 Ol>>  ¿

 Ol>> becomes

 Ol>>    🤖
 Ol>> 🦾⚙️
 Ol>>   🦿

 Ol>> I guess I'm bored (it's raining for days and it won't stop).

 d> Actually, I think it does.

 d> The quoted message that I saw from the Robot quoted the UTF-8 versions of
 d> the characters.

 d> (Its just a re-pasting of the quoted message, and I dont think hpt does
 d> anything with those chars.)

 d> I wonder why you didnt see it that way?

Right, the characters were copied unmodified, but without a CHRS: kludge my reader uses CP437 as the default encoding (which works best in most cases).

Quoting FTS-5003 (.001):

  Incoming messages without "CHRS" control lines should be considered
  as being written in pure ASCII, but may be treated as being written
  in some default character set or character encoding scheme. Such as
  IBM codepage 437, IBM codepage 866 or UTF-8. It is recommended that
  message readers offer the user the option of manually selecting a
  different character set or encoding scheme for these messages on a
  per-area, per-message or other basis.

If the Hub Robot did use the original CHRS kludge in the reply, there would be a better chance of getting the extended characters displayed correctly. No idea if that is easy to do with hpt or if it requires some weird workarounds. Not that important though as most test messages don't include characters >127.

---
 * Origin: . (21:3/102)

.