Bug Stomp

(Is there a way to restore accidentally deleted bots? - Could bot holdays be noted in the transcripts too, please?)

Special characters like umlauts are not shown in popup chatboxes. (They seem to get into the transcripts, though. Can't really test for I don't know how to initiate a popup chat with my bots.)

In one Debug session (Peter Wolff; started a few minutes ago), the initial "Hello" to the bot in my name was considered Blab.


[Edit:] Just got a popup chat with one of my bots, so I can tell more.

Special characters as HTML entities are no problem in the popup window; special charactes as themselves turn up in both transcripts, and don't influence the keyphrase recognition, but they and everything that follows is omitted from my responses in the popup window (already in the page source).

I just fixed the blank memory bug and the chrono bug.

Mome - to clarify, do those special characters as themselves not reach the page source? Or do they reach the source but are not rendered on the page?

Also - does that affect the direct chat page and debug or just the pop-ups?

An update on what I said earlier - I looked into the code and gossip doesn't just check once like I thought - it goes through the usual process of looking for a valid response before moving on to an xnone.

Good suggestions. I've added them to my fix list.

Sorry if I wasn't clear enough.

The special characters are NOT in the page source.

That affects ONLY the popups, NOT the direct chat pages, and NOT the debugs.

(But it is fixed meanwhile, thank you!)

Thanks for the clarification - I'll look into it.

I have an answer for the hello in debug going to blab - that's actually a FAQ. It only treats hellos as greetings when you haven't chatted with the bot in an hour or two. Otherwise the bot considers the conversation ongoing and sends it to blab. You can see the AI Engine recognizing it by looking for "isHello" I think, in Debug.

I know the FAQ page. What I meant is that on the page that opens directly after clicking on "Debug" there is a message allegedly from me to the bot that is "Hello". And this very first message was "considered BLAB" in that case.

On a second thought, this might also explain why bots don't seem to understand when one answers their "Hello" with a "Hi".

Right, a "Hello" is sent from a user when the Debug page opens, which follows the same xhello/blab rules I mentioned above. I suppose an improvement there would be to leave out the "Hello" and have the bot serve up an xinitiate.

Edit: I've made this change.

In other news, I got the Combined Bot Template to just under 20,000 Keyphrases now from the original 36,000. Still tons of work to do there, and it's inspiring some good ideas while I work.

Thanks, now I see my mistake - I had talked to my bot less than an hour before. Should have thought of this.

I've found something strange about the popup texts that end before a special character:

- Most browsers (both on Windows and Linux) show the mentioned behavior (special character and everything that follows is omitted even from the source)

- Iceweasel works as it should

- Konqueror works like most browsers with the default settings. When I set the character encoding of the main window to UTF-8, it shows the complete text in the popup windows, but strange characters instead of the given one; when I change the character encoding of the popup window by context menu, the special character is shown as itself

The following might therefore be related: When I look in the source of any personalityforge page (normal or popup), I don't find any charset directive there.

I wonder whether this is a bug or whether I simply don't understand the concept of (vp):

"what are you talking about" doesn't match "what are you (vp)", but "what are you telling me" does.

(And "what are you telling me" when tested against "what are you (vp)" fills "you" into (postkey).)

Btw, would be nice to have a pattern that would match (vp) as well as a single word that is a verb form.

That's probably it. I've updated the doctype declaration and the set the charset to ISO-8859-1 which should be the default and seems to be correct for displaying umlauts and the like. Do you see a difference?

Sorry, it is still not working. The charset is still missing in the popup windows.

(And there seem to be two spaces missing in the "big" pages, when I compare them to other websites; Firefox renders that source line in red)

Seems to work now. Thanks, Professor!