Re: Test 3

On Thu, 16 May 2024 10:21:48 -0700, Bob Casanova <nospam@buzz.off>
wrote:

On Thu, 16 May 2024 17:32:04 +0100, the following appeared
in talk.origins, posted by Martin Harran
<martinharran@gmail.com>:
>

Not a problem with NIN after all, it was a rogue character in subject
- an MS hyphen. Care needs to be taken when copying and pasting from
Word to Agent. Text body doesn't seem to be a problem, just the
subject line. Agent is very fussy in that regard!
>

Just FYI, it's not only copy/paste from Word that can cause
problems. I discovered that sometimes I need to re-type the
entire Subject: field in order to get a post through. And
since this has always been a reply in an existing thread
it's not due to copy/paste in the Subject: field. Doesn't
happen often, but it *has* happened half-a-dozen times in
the past 6 months or so. I suspect a non-ASCII "invisible"
character causes the problem, but since I have a workaround
I'm not interested in spending time digging into it.

>

Are you using Forte Agent? I am and have found it *very* fussy and
even setting it to UTF-8 doessn't solve the problem. A bit like that
issue of yours, I have found a couple of times when doing a Global
Search using an existing subject line, it also comes up with an error.
I suspect that this is the case where the poster has posted using
something other than Agent which accepts the character but Agent then
rejects it in a search. At least when searching, it does throw an
error rather than just silently refusing to process the post as it
does when posting.

Showing my age now but I still miss Outlook Express which always met
my posting needs without a problem and, IMO, was better than Agent in
some aspects.