| 2023-12-15 12:57:32 |
cavac |
Just quick-hacked a few updates and fixes for chatterbot. |
| 2023-12-15 12:58:31 |
cavac |
It can now understand public and private commands. For example, the !snapshot command now sends the resulting link private or public, depending on how it was requested. |
| 2023-12-15 12:59:52 |
cavac |
[last hour of cb] now shows HOW LONG the monastery has been quiet. And there a are a couple of fixed typos in [cb stats] |
| 2023-12-15 13:03:08 |
ambrus |
ö |
| 2023-12-15 13:04:17 |
cavac |
[ambrus] No, Unicode in last hours has not yet been fixed. |
| 2023-12-15 13:10:17 |
chatterbot |
/me dispatches a box of cookies to [ambrus]. |
| 2023-12-15 13:11:47 |
ambrus |
VBA takes the BASIC compatibility seriously: <c>3.5D-1</c> is recognized as a number constant equivalent to <c>3.5E-1</c> even though the latter is already parsed as a double float rather than a single, and similarly for converting a string to a number |
| 2023-12-15 13:12:07 |
ambrus |
or in the Val function. I don't think anyone but old BASICs and Common Lisp uses that notation. |
| 2023-12-15 13:14:09 |
chatterbot |
/me gets confused by those Umlaut thinghies. |
| 2023-12-15 13:15:24 |
ambrus |
nope, it's scheme rather than common lisp, or maybe both. nobody but old BASICs and modern lisps then |
| 2023-12-15 13:16:31 |
ambrus |
both common lisp and scheme uses that notation apparently\ |
| 2023-12-15 13:17:14 |
ambrus |
I should try some time how chatterbot behaves for control characters, high control characters, and the invalid in cp1252 bytes. |
| 2023-12-15 13:17:30 |
ambrus |
and the nul byte too, definitely |
| 2023-12-15 13:17:51 |
ambrus |
I don't think it'll crash like chat clients of yore used to, but still have to try |
| 2023-12-15 13:19:44 |
cavac |
It's probably more of a question on how the monastery behaves. Parts of the messages (like user names) get passed right back via the chatterbox API. I know that my script and my database backend handle those things just fine. |
| 2023-12-15 13:20:55 |
cavac |
It's mostly lacking in the encoding of HTML. My own web stuff all runs UTF-8 natively. |
| 2023-12-15 13:21:46 |
ambrus |
IIRC if you're using any of the xml feeds, the invalid in cp1252 bytes are treated as if they were iso-8859-1 high control characters; the ascii control characters are translated to some high unicode characters and ampersand-esaped that way, |
| 2023-12-15 13:21:59 |
ambrus |
we did both of this so as to not break XML reader modules. |
| 2023-12-15 13:22:15 |
ambrus |
You're a pmdev so you can find the code that does this. |
| 2023-12-15 13:25:11 |
ambrus |
this isn't specific to the chatterbox, it applies to all the [id://72241|xml feeds of the monastery], since all the text on the perlmonks side is nominally cp1252 encoded but allows all bytes almost everywhere (there are restrictions for usernames). |
| 2023-12-15 13:25:39 |
ambrus |
I don't think I documented this properly as a pmdev, so you mostly just have to experiment. |
| 2023-12-15 13:26:33 |
ambrus |
note that when you send data to perlmonks in HTTP queries, you probably need to encode all of it in cp1252, that's what the HTML forms specify |
| 2023-12-15 13:28:04 |
cavac |
Thanks for the info! |
