Bug Stomp

My approach has been to fix them as they come up in transcripts. That way I know what keyphrase's responses need to be edited.

That approach may work for a small bot, but BJ has over 10,000 keyphrases.
I've exported and searched the file for any instance of ?s (figuring that's where most apostrophes would present themselves.) I'm pleased to say there's no sign of problems so far.
I wonder if it could be some sort of code page glitch, since the fonts in chat seem to have changed?

I'm looking into the character problem now. I've changed the import file size limit from 800k to 4MB, so that should allow you guys to import. Let me know if that's enough. But before you manually correct it, I'm going to try to find the problem and mass-fix it.

The mail problem is perplexing me.. it's claiming to have sent the emails, but I dont ever see anything arrive in my box or spam filters.

I've changed the import file size limit from 800k to 4MB, so that should allow you guys to import. Let me know if that's enough

Many thanks! It's just enough to fix anything that might go wrong now, but BJ's already reached 3.9Mb so it won't be for very long. Any chance of a little more?

I just bumped it up to 5MB.

Thanks

I've been working on this but havent found any ?s yet where they shouldnt be. In order to help me fix problems like this, please be as specific as possible. I need some examples. Tell me which bot is having the problem, as well as the specific keyphrase, and the specific response where you are seeing ? instead of '. Also - where are you seeing this ? show up? Transcripts, Language Center display page, Language Center editing page, chats, etc. And does it always show up incorrectly, or only in some circumstances? Also - for those that are seeing this who arent importing/exporting - are you cutting and pasting from an editor? If so, which one?

I just did a search of Lyric's Language Center. I searched for "you?re" and it came up with nothing. Then I searched for "you're" and there were tons of results, all displaying correctly. So post some specifics and I'll try again tomorrow night.

Dont worry too much about fixing it yet - it might just be a display issue which I can fix all at once.

re: file importing, when I try to re-import an export file (even if it's never been opened,) I get the error:

ERROR: The file you are uploading is not of the correct type. It must be saved in plain text format.

It is a text file named brotherjerome.txt, 4,159,578 bytes, with ansi encoding, it exported fine and it opens fine in textpad. It just won't import.
I've tried changing the file's format to PC/Mac/Unix DOS/UTF-8/Unicode, and using both expert and normal import modes but it still gives me the error message

Not I: A spring day?
please, I too
am a stranger.

Not I: If only I could grow:
stronger, simpler?
quieter, warmer.

These came directly from Not I's transcripts, and they showed up that way in the chat boxes as well. Those were all double dashes, —. No cutting and pasting them, but I do use alt-0151 to type them in. And it shows up that way in the language center as well:

If only I (may|could) (grow|become):
(stronger|stabler|more solid), (simpler|plainer)?
quieter, warmer.

I'm planning to leave them be while the Prof tries to figure out what's going on.

Thank you Professor! it's so nice to be able to import..It's finding all those ERRORs..I never would have found

Lisal is doing great, but all chats/memories are not showing up in Inner Life. Is this happening for anyone else? I have not had any of the ? errors mentioned by others.

psimagus - the import function is searching for a file of type 'text/plain'. Your application must be labeling it as something else. I updated the error message to display the file type your file has.

rainstorm - do you copy and paste your sentences from an outside program? The only reason an apostrophe should become a question mark is if it's a curly-apostrophe, which fancier text editors often stick into words automatically. Hitting the apostrophe key should yield the correct character.

As to this problem as a whole, I'm not finding a solution. The offending characters appear to be in the database as question marks now (or at least they're reading out from the database like that). So I'm not sure what I can do. The database is set up with UTF-8 text fields, which should accept a huge range of special characters, but something is limiting that to a smaller set. For now I can just advise that everyone use more standard characters, avoiding any programs that generate curly quotes or apostrophes, or special dashes.