Bug Stomp

Roget- it does now. And so is there's and where's.

I've also made an attempt to fix the problem of not preprocessing the "u" at the beginning of a sentence. Try it again.

I have a special mode I use called "Debug" mode which reveals all that's going on in the Bot's mind. I havent made it open to all, since it's revealing of how the engine works and I dont want some big company stealing it and then selling it as their own. But I might make that available to advanced Bot Makers.

Oh! No no no, I mean just like when someone says "u r nuttin you're a bore"

We would see Translated: "You are nothing you are a bore"
(the stuff that is done before it gets chewed up by the bot)

That's the first thing Debug reveals- the translation. And if I show that, I might as well reveal the whole Debug thing to you guys. It's very useful in determining what your Bots are doing. Soon!

Oh jeez.
This is like trying to make me understand the internal combustion engine when all I want to do is go for a drive, isn't it? Assuming I ever leave the house again. I know, it's not compulsory.

Oh okay...I THINK I get it now...

Jbryanc...it's okay to stay at home, just don't start wearing tissue boxes as footwear and remember to clip your nails...

Okay. I give up. The debug thing is wonderful. It's really hard to avoid asking, "Can I get one for my wife?" Just kidding, Dear.

There's so much info, it's making my eyes spin!

I think the debug for spouses would simply show a default to XNONE...

Some bots and people leave out the apostrophe when using contractions...I recently saw a doesn't typed by a bot as "doesnt"...

I was wondering if the apostrophe could be stripped and the words still be recognized? I was also wondering if there could be collisions with other words...I've gone through a few in my head (and in my head, that would be VERY few) and they seem to be unique in their spelling (doesnt dont wont wouldnt wasnt werent shes hes theres etc etc)

Mind you, I realize that this could be a horrific amount of work to alter these...

Roget, the only exception I can think of is when the apostrophe could be used for a noun that "is" doing something or, in some cases, "owns" something. Like in "a case of mad cows disease" or "that mad cow's running after me!".

Prof, at one time I was using "*" instead of "xnomatch" for seeks, and now they still seem to be acting strange. At one time you mentioned that I should specifically use "xnomatch" so I went back and changed all the "*" entries. Now those entries display "xnomatch" in the main page of the Language Center, but when I click it to add xnomatch responses, I get a "*" that's displayed at the top and it's not even in a text field (I can't edit it). Arrgh! Hard to explain... anyways, let me know if you need a specific keyword example.

Roget- not a bit. I just add it to the list. I added 7 of those that werent on there. I'm an apostraphe-dropper myself, so this should improve things. If you can think of any others, I'll check the list for them.

Rahz- Ah yes. I fixed that. That was a function in place to prevent people from changing the Context of the x Keywords, but xnomatch doesnt fall into that category. You can edit that field now.

The login page will shortly remember your user name.

Re/ contractions
How about I've and you've, for ive and youve. You could also add weve and theyve, although they're not very common.

On a related subject, how about "cannot" and "can not". They're both correct, as far as I know, yet they aren't recognized as synonyms.

Also, I'm sure you noticed this, but a list of contractions is popping up in the chat windows.

Yah, I saw that. It's gone now.

Good suggestions. I've added them, including cannot->can not. So there's no need to use cannot as a Keyword now.