Re: Next Sentence (NS) glitch; was Re: More on Tame

[Xywrite3plus@xxxxxxxx]

 In a message dated 12/12/2002 2:11:44 PM Eastern Standard Time,
holmgren@xxxxxxxx writes:
> Except for the W2K-only part, I'd look first at the troublesome files/
> sections
> with a DOS-level file lister. They may have hex 0D or 0A by themselves (
> lone
> cr, lone linefeed) -- eminently possible if the docs weren't produced by
> XyWrite in the first place.
>
Thanks, Robert, that did the trick. (Thanks to Adriano, too.) But List shows
something more bizarre than hex 0D or 0A. In fact, what appears as a period
on screen is the three-byte string hex FF 32 45. I haven't had the time to
poke into your documentation in ctrlchar to figure out why Xy would display
that sequence as a period.

It may be worth pointing out that the file comes from a txt file probably
saved by, what else, M$Word (though I can't rule out that the conversion came
from an editor here using Word Perfect). Mind you, not all the "foreign"
periods come in this way, just some of 'em. I don't think W2K is to blame
anymore.

Anyway, thanks. I'll have to add this to my strip routines in the future.

>Try dropping NI, just for the heck of it.

I had tried that, to no avail.

Peter Brown
psjrbrown@xxxxxxxx

> > long ago I
> > dedicated a few keys in my keyboard file to moving the cursor to the
next
> or
> > previous sentence. The relevant entries in the keyboard file are:
> > XX=NI,NS,CR
> > to get to the beginning of the next sentence..., and
> > XX=NI,PW,PS,CR,NS,CR
> > to get to the beginning of the sentence preceding... These work most of
> the
> > time, on most files. Occasionally, though, just with
> > some files, or with certain parts of some files, the cursor jumps to the
> next
> > or preceding *paragraph* (not the next or preceding sentence). I see
> nothing
> > in expanded view that could account for this, and it never happened
before
>
> > Win2000. Anyone have any ideas about troubleshooting this?
>